What's Local Pre-caching?

  • Updated
Feature availability 🛈
⭕ Personal ⭕ Shared ✔️ Suite

This feature allows you to pre-process your library so you don't have to wait for the different views to load, which can drastically improve the browsing experience. It's called "Local Pre-caching," and works similarly to the Metadata Harvester that processes the Shared Content Metadata.

Start Pre-caching dialog.

However, there are some significant differences – the Local Pre-caching doesn't require any storage setup because everything is stored locally. Consequently, it's only accessible by the instance that runs the tool, not the entire team. 

Keep in mind that if you need additional features, such as indexed search and metadata filters, you'll have to utilize the Shared Content Metadata.

NOTE: Depending on the size of your asset library, the Local Pre-caching may take a long time to process it. That's why it's best to start the process when you're done working for the day or even during the weekend.

How to use it?

The Local Pre-caching is accessible from the "Tools" dropdown, and it caches locally the following metadata:

  • Preview thumbnails for all supported formats.
  • MAX assets:
    • Max version.
    • Renderer.
  • C4D assets:
    • Cinema 4D version.
    • Renderer.
  • MAT assets:
    • Materials (if dedicated 3ds Max is available, shown in Previews Panel).
  • RVT assets:
    • Revit version.
  • RFA assets:
    • Revit version.
    • Family info (host, family details, etc., shown in the Asset Details Panel).
    • Family types with parameters (if dedicated Revit is available).
  • CUAP assets:
    • Asset details (UE version, etc., shown in Asset Details Panel).

IMPORTANT: To harvest the 3ds Max and Revit asset metadata, you’ll need to set up the dedicated instances for each from the Local Pre-caching dialog.

Local Pre-caching dialog.