Tweet
Quick question - right now, I believe swarm sends all assets over the LAN to the swarm workers from the singular workstation that launched the job. Now most of this stuff (textures, proxies, etc) are located in shared network locations, so I was thinking it might be quicker and easier for each swarm to grab those assets from our file servers instead of directly off the workstation sending the job. I know there is a variable I can enter in the swarm config (VRAY_ASSETS_PATH) but my question is: does this command also search all sub-directories? We have assets across 3 various drives and deep into folders, so putting in direct paths isn't possible for all assets in a project, but I'm hoping/wishing the (VRAY_ASSETS_PATH) can search sub-directories?
-
-
SWARM will transfer assets if the render nodes cannot see them on the network. If you add your assets with UNC paths - make sure that "vrswrm-service" / display name "V-Ray Swarm" is running with an account that has permissions to access the respective assets' locations. By default, the service runs with "Local system account" that has no share/network permissions.
Regarding your other question - VRAY_ASSETS_PATH variable doesn't work with sub-directoriesIvan Slavchev
SysOps
Chaos Group -
ok, wait, so if we used mapped drives (no UNC), then the assets will come from those locations directly? That's basically what we have and what we would need to avoid the two-hop transfer (mapped server drives to submitting workstation, submitting workstation to each swarm node)
Comment
-
Mapped drives should work too, but you'll still need to run the SWARM service with a user that has permissions to access the assets over the network, since a mapped drive is not really a local path.Originally posted by delineator View PostIvan Slavchev
SysOps
Chaos GroupComment
Comment