Tweet
Well I guess this is one that might be easier to implement when vray goes standalone, but anyways:
What I want is for the spawner to run as a service (so its controllable localy and remotely through the services part of the computer management).
Most importantly, I would also like it to be set as low or below normal priority, and if possible, avoid the whole "vray_server_scene.max" app running in the task bar.
Even better might be that one machine is set up as a manager (as with backburner), and this machine runs a "über-spawner" app that handles all connections (and licenses too
). Then all clients connect to this when vray is run as the active renderer in ones favourite 3d suite.
Feel free to chime in and lecture me on better sollutions
What I want is for the spawner to run as a service (so its controllable localy and remotely through the services part of the computer management).
Most importantly, I would also like it to be set as low or below normal priority, and if possible, avoid the whole "vray_server_scene.max" app running in the task bar.
Even better might be that one machine is set up as a manager (as with backburner), and this machine runs a "über-spawner" app that handles all connections (and licenses too
). Then all clients connect to this when vray is run as the active renderer in ones favourite 3d suite. Feel free to chime in and lecture me on better sollutions
