Page History
...
| Fancy Bullets | ||
|---|---|---|
| ||
|
Distributed Rendering of Fluid Caches for PhoenixAnchor drCaches drCaches
...
A common problem when setting up DR is that by default Phoenix looks for the cache files in the same directory as the scene file using the $(work_path) keyword. However, at the start of a network render, the scene file is copied to all render machines on the network to a new location (e.g. C:\Users\user\AppData\Local\backburner\Jobs\) while the cache files are not automatically sent to the host machine(s). They are not sent because they may be really huge and may overload the network and the disk space of the host, and would take too much time to transfer, negating the proficiency of DR. This is why when rendering begins, if the hosts are looking for the cache files in the same directory where the scene file is, the cache files won't be found.
...
| Anchor | ||||
|---|---|---|---|---|
|
Mapped Drives and UNC Paths for Texture Maps and Other Rendering Assets
...
If you are using mapped drives or UNC paths for your scene assets, you should set up a "Log On" account for the V-Ray spawner service, otherwise, the textures or any other external assets won't be accessible. To set up the Log On account, open the Services applet from the Control panel (Control panel > Administrative Tools > Services) and find find "VRayMayaSpawner 20nn" then right-click to expand the drop-down menu and choose Properties. Go to the the Log On tab and instead of the default Log on as local system account choose This account and put the name of an account that has adequate privileges on the machine and access to the shared resources over the network.
Alternatively, you can use the automatic asset transfer mechanism of V-Ray as described above to send the required assets from the client machine to the render servers.
...
