If I run “V-Ray DR spawner” from the Start Menu on my slave machines all works correctly.
If I run “V-Ray spawner” as a service on my slave machines all works except that slave buckets don’t render textures.
Commonly I start the spawner from the Start Menu (not as a service), and all works, but for a reason I really don’t understand just one of my slave machines (that is exactly like the others) doesn’t parteciapte on the distribute render if I use the spawner from the Start Menu, while it does if I use it as a service, but doens’t render textures
Do you use mapped drives for your texture paths? If so you have to use UNC paths because when vray starts as a service it will not have any mapped drives available to it (windows limitation - mapped drives are for logged in users not services). Alternatively if you use UNC paths but your company implements security policies make sure to go into the windows service settings and change the user from “system” to your username.
I am having a similar issue. Our IT dept recently upgraded one of our machines from Vista to Windows 7. Now when I distribute render to this computer it drops the textures. The buckets show up and render, just no maps. Does anyone have a fix idea for this?
interesting. I’m sure my personal login has administrative privileges, since its my own machine and I installed windows personally. I’ll give it a check.
EDIT: yes my slave machine’s login is an administrator.
I had this with windows 7 but it was to do with loading irradiance maps when network rendering. The solution is to lower the user security in windows 7.
Similar problem here. Three render nodes have been working great for over a year since they were built. Then about a month ago two of the machines fail to load textures/proxies when running as DR nodes. Funny thing is all the resources are visible in Windows Explorer. All the drives are mapped. I think I have DR running as a service. I’ll try removing the service and running DR from the Start menu to see if that makes a difference… Yes indeed. Resource loading works correctly when DR is run as an application, but not as a service. Whew. At least I’ve got a work-around now. Thanks Daniele.
Same problem here, 4 render nodes all running max 2010 64bit. I’ve tried both mapped network drives and UNC paths with no luck, no firewalls all admin permissions. Only way i can get textures to work on DR now is to login manually and start DR spawner from max directory. Which is fine it works well just takes 5 minutes to setup rather than 1
Not sure if this will fix issue with Win7 … been using this in WinXp to have the spawner service run under specific credentials (so drive mapping associated to user profile is recognized … even if machine is logged off)
Applying Log On credentials to the VraySpawner service.
1) Stop VRaySpawner## service if started.
2) Right-click on the service > Properties > Log On tab
3) Apply your username and password so that the service starts with your credentials.
4) Start VRaySpawner## service.
5) You should then see the vrspawner##.exe and 3dsmax.exe processes in the Task Manager associated to the designated user … rather than with the default “System”.
