Versions Compared

Old Version 6

changes.mady.by.user Slavina Nikolova

Saved on

compared with

New Version 7

changes.mady.by.user Slavina Nikolova

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Fancy Bullets
typecircle
  • Try using the latest versions of Phoenix and V-Ray.
  • Confirm that the version numbers are the same on all DR machines.
  • Make sure the V-Ray Render Settings → Settings → Distributed Rendering → Transfer Missing Assets option is enabled. This option allows render servers to automatically download missing caches from the client machine. For more details, see Distributed Rendering of Fluid Caches for Phoenix below.
  • In case you are using a shared network folder, check if the simulation caches are shared on a network location that all the machines can see. Note: They all must have permissions to access this network folder. For more details, see Distributed Rendering of Fluid Caches for Phoenix below.
  • Confirm that your V-Ray Spawner is started as an administrator on the remote machines. For more details, see Mapped Drives and UNC Paths for Texture Maps and Other Rendering Assets below.
  • Make sure your V-Ray Spawner is run as the same account as the one you are testing the permissions with. Your local account might be able to see the shared network folder but the spawner might be started with a different user account which doesn't have proper permissions.

...

A common problem when setting up DR Distributed Rendering 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.which will greatly reduce the performance of Distributed Rendering.

To automatically send the caches to a host machine(s), you can use the Transfer Missing Assets option, located in V-Ray Render Settings → Settings → Distributed Rendering tab. This way, the render servers will automatically download the missing caches from the client machine. For more information on Distributed Rendering settings, see the Distributed Rendering page. Keep in mind that the transfer of large cache sequences may slow down the Distributed Rendering process.

In case you don't have enough space on the machines, you can The solution is to move the cache sequence to a shared folder on the network or a mapped network drive and set its path in the Input rollout, using a network-visible UNC path (a path that starts with \\). You can also browse from the Input rollout Path options.

If you are not using a UNC path or a mapped network drive, and instead your path points to a drive on your local computer or is one of the Phoenix keywords ($(work_path), $(scene_path), $(implicit), $(scene_dir), etc...), you will receive a message that states "You are using local machine Input path with distributed rendering!".

...