View Full Version : netrender system exception
04-27-2008, 05:09 PM
Im trying to enhance the render capabilties of a render pass manager, however when I try to connect to the manager I get a system exception...
This is with max 9 and backbuner 2008.1 also max 2009 same backburner.
m.connect #automatic "255.255.255.0"
** system exception **
Any help would be greatly appreciated!
04-27-2008, 05:18 PM
try connecting manually and/or specifying the port; "... port:3234"
netrender access from maxscript is, sadly, broken left and right. I haven't tested with backburner 2008.1 as of yet. Have you tried with backburner 3 / 2? If so - did that work ok?
04-27-2008, 05:35 PM
I tried with the specific port, also same result. When I tried a port that isnt correct it would not connect(as intended) but it would not give a system exception.
The reason id like it to work with 2008.1 is because this is a script I will distribute so users need to be able to have it work for them in this version.
Also on manual connect it, it gives the same error
but when I look in the backburner manager log it says :New client 192.168.2.58 added to client list...
04-27-2008, 10:36 PM
Yeah, I'm just curious if this is something -new- to BB2008 / 2008.1 or whether you get that error in v3 / v2 as well. Obviously supporting what the users use is great, but if ADSK broke things in BB2008 / 2008.1 ..
04-28-2008, 01:07 AM
I was originally working with backburner 2007 but same error, then I tried 2008. Im thinking it could be something with my setup but I am able to network render just fine through the max interface...
04-28-2008, 11:32 PM
I could give you the advice I was given from the AD help desk... buy a third party render managment solution... ( we've over 80 render nodes. )
We're still on BB2007.0.1, but looking at going to 2008. I'm very interested in the outcome of your issue....
04-30-2008, 02:38 AM
Reinstalled windows and everything works fine now, <sarcarm> easy fix </sarcasm>
04-30-2008, 02:38 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.