Tweet
In our office, we have some dedicated rendering computers, but the vast majority of our render nodes are user workstations. And of those, quite a few may be either logged off or idle. However, there is no way that I can see of to filter for those optimum states when choosing distributed nodes for a render job.
It would be better, I think, if render node tag management could be a dynamic, rather than a static process. For example, it would be helpful if tags could be set automatically when a user logs in or logs out, so that machines could be tagged as 'Logged on' or 'Logged off'. That way users could filter for machines that are more efficient than others.
Currently, one could code a program or script to edit the VRAY Swarm config file at "C:\Windows\System32\config\systemprofile\AppData\ Roaming\Chaos Group\vray-swarm\work\vray-swarm\swarm-config.json". However, this file resides in a very protected location so it's not a simple matter to edit this file via script. It would take either a service running with elevated access credentials, or changing the permission settings on the config file. (Considering its location in the OS folder, this is not a good idea.) Would it be possible to locate the swarm config elsewhere: maybe C:\ProgramData\ChaosGroup\...? Even the Program Files folder would be better than within the OS folder.
It would also be great to dynamically tag for certain computer attributes such as, CPU count or amount of RAM.
It would be better, I think, if render node tag management could be a dynamic, rather than a static process. For example, it would be helpful if tags could be set automatically when a user logs in or logs out, so that machines could be tagged as 'Logged on' or 'Logged off'. That way users could filter for machines that are more efficient than others.
Currently, one could code a program or script to edit the VRAY Swarm config file at "C:\Windows\System32\config\systemprofile\AppData\ Roaming\Chaos Group\vray-swarm\work\vray-swarm\swarm-config.json". However, this file resides in a very protected location so it's not a simple matter to edit this file via script. It would take either a service running with elevated access credentials, or changing the permission settings on the config file. (Considering its location in the OS folder, this is not a good idea.) Would it be possible to locate the swarm config elsewhere: maybe C:\ProgramData\ChaosGroup\...? Even the Program Files folder would be better than within the OS folder.
It would also be great to dynamically tag for certain computer attributes such as, CPU count or amount of RAM.
Comment