Page History
This page provides information on Distributed Rendering with Chaos Phoenix FD.
Overview
...
Distributed Rendering (DR) is a technique for dispersing rendering jobs within a single frame across multiple computers in a network. There are different approaches to doing this but the main concept is to reduce the render times by dividing different parts of the rendering task and giving each participant different parts to complete. The most common way to do this is to divide the frame to be rendered into small regions and giving each rendering machine one after another until the entire frame or job is complete. Then the results are combined into the final image.
UI Text Box | ||
---|---|---|
| ||
Note that a distributed simulation, where distributed simulations in which different parts of the same simulation are calculated simultaneously across several machines , is currently are currently not implemented. However, you You can use Phoenix 3.0's the Simulation licenses to run many simulations on separate machines without using the Graphical User Interface. This way you can also simultaneously run many different simulations on different machines. For this usage of Phoenix FDaccessing the user interface and without engaging a GUI license. For more information on how to submit simulations that use only a Simulation license and how to do advanced scripting for more complicated tasks, see Simulation Without a GUI License. |
Setting up Phoenix Distributed Rendering using V-Ray
...
For more information on DR using V-Ray, see the Set up Distributed Rendering page.
Troubleshooting
...
If you're able to render locally but when using DR machines, the Phoenix fluid is missing from the buckets, please try the following:
Fancy Bullets | ||
---|---|---|
| ||
|
...
A common problem when setting up DR Distributed Rendering is that by default Phoenix FD looks Phoenix looks for the cache files in the same directory as the scene file using the $(scene_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 DRwhich will greatly reduce the performance of Distributed Rendering. 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.
...
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.
...