Hi,
Got Vray Next so uninstalled 3.6 on all the machines and installed Next on all the machines.
However strangely enough, atleast I thought so, when starting the new pc's the old spawner was still present and started a dummy 3ds max program. I always just copy the spawner.exe to the start-up menu. Removing the old spawner.exe and replacing it with the Next version solved this issue on all but 1 of the rendernodes.
I checked the start-up folder but it didn't contain an old 3.6 spawner.exe. I also couldn't find it as a windows service.
Could someone let me know what the name is of the service, incase I missed it. And also if there is another reason why the old spawner starts.
Backburner and DR jobs work fine once the old spawner has been turned off. The other pc's work fine aswell.
Thanks!
max 2016
windows 10
VrayNext
Got Vray Next so uninstalled 3.6 on all the machines and installed Next on all the machines.
However strangely enough, atleast I thought so, when starting the new pc's the old spawner was still present and started a dummy 3ds max program. I always just copy the spawner.exe to the start-up menu. Removing the old spawner.exe and replacing it with the Next version solved this issue on all but 1 of the rendernodes.
I checked the start-up folder but it didn't contain an old 3.6 spawner.exe. I also couldn't find it as a windows service.
Could someone let me know what the name is of the service, incase I missed it. And also if there is another reason why the old spawner starts.
Backburner and DR jobs work fine once the old spawner has been turned off. The other pc's work fine aswell.
Thanks!
max 2016
windows 10
VrayNext
Comment