Render to network shouldn't start manager and rendernodes
Posted: Fri Dec 20, 2013 11:42 am
Hi!
When using "Start netrender" in latest Cinema 4d plug. Monitor, manager and rendernode is starting up on my local computer where I run Cinema 4d. We have a renderfarm at our office and the last thing I want is to run a manager and rendernode on my local computer. If we run large renderings on the farm and a rendernode is startingup on my local, there could be errors in the renderings or my computer doesn't have enough memory to have a big scene in c4d up in the same time that a rendernode will use alot of memory.
Could you please change this behaviour on next update, or a setuptab where every user could decide on their own, if there isn't already an option like that?
Greetings
Tobias Gustafsson
When using "Start netrender" in latest Cinema 4d plug. Monitor, manager and rendernode is starting up on my local computer where I run Cinema 4d. We have a renderfarm at our office and the last thing I want is to run a manager and rendernode on my local computer. If we run large renderings on the farm and a rendernode is startingup on my local, there could be errors in the renderings or my computer doesn't have enough memory to have a big scene in c4d up in the same time that a rendernode will use alot of memory.
Could you please change this behaviour on next update, or a setuptab where every user could decide on their own, if there isn't already an option like that?
Greetings
Tobias Gustafsson