...
During rendering, whenever 3Delight encounters a non-optimized texture, it will create an optimized copy automatically. The optimized texture will be saved at the same location and will have the same base name as the associated non-optimized texture, but with a .tdl extension added. This process will skip any texture that have the .tdl substring in the file name (e.g. texname.tdl.tif and texname.tif.tdl (as ) as they will be considered as already optimized. Note that 3Delight also detects if a source texture has changed since the optimized copy and will automatically re-optimize it.
| Warning |
|---|
For the automatic optimization to work in the context of teamwork, the directory or directories where the textures are located must have write permission not only to oneself, but also to other users (so the optimization process works for them if needed while rendering). The non-optimized texture files themselves do not need to have write permissions as 3Delight only access them for reading and never modifies them. |
...
The network cache content is updated automatically: when texture files are modified on the file server, the local (cached) copies will be automatically updated the first time they are needed for a rendering. If there is no more space in the cache, copied textures are removed to make space for incoming textures by following the Least Recently Used (LRU) principle.
By default, the Network Cache in not active. We recommend you turn it on. You only need to specify its maximum size (we recommend at least 50GB). This is done through the 3delight.config configuration file.
...