Local Assets Cache Setup

This tutorial explains the setup for keeping a local copy of the assets needed for rendering.

Overview

V-Ray Next provides a setup for keeping a local cache of assets required for rendering a scene. This can help prevent locking asset files for editing while rendering or can help reduce network traffic when the assets are stored on a shared network location.

• Assets are copied locally to avoid locking the files while rendering. Locking the files prevents other artists from editing them or replacing them with newer versions of the assets.
• While rendering, an asset may be requested by the renderer a number of times, which can put stress on network traffic, especially when the files are stored on a network location and hundreds of render nodes are requesting those files.

VRAY_LOCAL_CACHE_LIMIT_TYPE - Specifies a local cache for rendering assets. The assets are copied locally for use by V-Ray, so that the original assets can remain unlocked for editing in other applications. This variable specifies the limit type of the cache, while VRAY_LOCAL_CACHE_LIMIT_VALUE specifies the limit size of the cache. The limit is not applied during rendering, files are cleaned up after the render finishes. By default, the local cache is written to a vray_assets_cache folder placed (and automatically created) in the user's temp directory. The VRAY_ASSETS_CACHE_PATH variable can be used to specify a different location for the local cache.

-1 - disabled (default)
0 - no limit
1 - limit by age in hours. Files older than N hours are deleted.
2 - limit by maximum size in gigabytes.

VRAY_LOCAL_CACHE_LIMIT_VALUE - A limit to the local asset cache. The meaning of the value depends on VRAY_LOCAL_CACHE_LIMIT_TYPE. Setting VRAY_LOCAL_CACHE_LIMIT_VALUE to 0 will effectively delete all cached files after every render.