Open philstopford opened 6 years ago
'absolute paths', 'shared directory' - those are not needed because vray will transfer as stets by itself. 'render only on nodes', 'abort rendering on missing asset' - those sounds like a bug.
I was hoping those two options would allow for already-available assets to be used in case they are found. This would allow, for example, large image files to be used without them having to be transferred to each node - the nodes could pull from the available paths. That's what 'absolute path' suggested to me - if d:\assets\file.png (for example) was being used in the master, the nodes would look for d:\assets\file.png locally.
The 'shared directory' was less clear to me, but it looked similar to the idea of absolute path.
Neither seemed to consider mixed farms (e.g. Windows and Linux, or Windows and Mac).
For the options, some didn't seem relevant in the non-transfer modes (e.g. the cache). It might be that all are getting hidden when only some should be (assuming you want to enable these non-transfer modes).
@philstopford vray will cache assets on nodes and re-transfer only if they have changed.
Switching from V-ray transfer to 'absolute paths' or 'shared directory', a number of options vanish (e.g. 'render only on nodes', 'abort rendering on missing asset') that would seem relevant.