Skip to main content
Version: Reality 5.5

Cache Management

Effective cache management is an important aspect of the production pipeline, particularly for studios that operate multiple large projects.

When a project is launched for the first time, Reality Hub generates a copy of the project in the configured cache folder of each Engine, located in c:\cache by default.

In following launches, Reality Hub automatically checks for any modifications made to the project in the shared folder and updates all cache copies to reflect those changes.

In addition, Reality Hub verifies whether the disk containing the cache folder has sufficient free space for the necessary operations.

If there is insufficient free space, Reality Hub automatically attempts to free up more space by removing cache copies of other projects, starting from the least popular one.

info

The Popularity number is a metric that reflects the level of demand for a particular project. If the Popularity number is high, it indicates a greater degree of the project's popularity among users.

Project Cache Example

The Cache section can be accessed by navigating to Main Menu > Configuration > Engines > Hosts > Cache

You can filter and delete cached project files via the Project Cache menu shown above.

info

Deleting a project cache will not delete the original project.

info

Please keep that in mind, the recommended workflow requires working with network storage for a more reliable, scalable, and secure pipeline.

You may get the "Cannot Free Enough Space" error in the following conditions:

  • If your general storage lacks enough space to handle your project.
  • A large project that doesn't fit into the cache disk alone.
  • A full cache disk, due to the content stored outside of the cache folder.
  • Malfunctioning disk, network, or other hardware-related issues.

In such a scenario, the Engine Status will turn red, indicating that the launch has failed.

To avoid such scenarios, we recommend that you routinely manage your overall disk space and project cache, particularly before proceeding to a live event.