- Wed Mar 07, 2012 4:49 pm
#353569
I am currently testing Maxwell for Rhino, and although I am fairly new to Rhino, I'm happy to see the Maxwell interface is pretty much the same across most programs.
One question I had is about renderings to the network (a new feature in 2.6.1 I see). I was curious if there was a way to bind a monitor IP address so we can render across our network? This was recently implemented in SketchUp and basically made it so that people in other offices could render to our farm without the need to manually add a job via the monitor. We would also like to turn off the manager and node auto-launch.
The SU solution was done via the ruby console (http://www.maxwellrender.com/forum/view ... 07&t=37967):
Any ideas? I noticed the log reads:
One question I had is about renderings to the network (a new feature in 2.6.1 I see). I was curious if there was a way to bind a monitor IP address so we can render across our network? This was recently implemented in SketchUp and basically made it so that people in other offices could render to our farm without the need to manually add a job via the monitor. We would also like to turn off the manager and node auto-launch.
The SU solution was done via the ruby console (http://www.maxwellrender.com/forum/view ... 07&t=37967):
Code: Select all
network = MX::Settings.network
network.start_node = true
network.start_manager = false
network.bind_node_to = '127.0.0.1'
network.bind_monitor_to = '127.0.0.1'
MX::Settings.save
Any ideas? I noticed the log reads:
Code: Select all
So I'm thinking something could potentially be coded in, correct? Any help would be appreciated.Maxwell: Sent .mxs to the Maxwell Network, the full command-line was '-monitor -addjob:"D:\Users\...\Desktop\city_rhino.mxs"'