why this code results in an error(system exception) in 2013 but not in 2011 ?
render_m = NetRender.GetManager()
render_m.connect #manual "10.0.0.60"
if( render_m.QueryControl #wait ) do
( render_m.getcontrol() )
render_m.wantControl = true
render_m.SetUpdates false
job = render_m.newJob()
job.name = maxfilename
job.suspended = true
job.submit()
job.state
render_m.Lock false
render_m.wantControl = true
render_m.SetUpdates true
render_m.disconnect()
AAUUUUHHGGGG…
Me too… just bought and installed 2013 and it’s a nightmare…
FSM_Connected_Manager = NetRender.GetManager()
FSM_Connected_Manager.connect #manual “qmanager”
NewNetworkJob = FSM_Connected_Manager.NewJob()
NewNetworkJob.name = “test”
NewNetworkJob.submit()
== ‘CRASH’
WTF autodesk?
i gave up on the NetRender interface a long time ago. which is why i now automate the network render dialog. I shared the code I use in this thread. As a bonus, it will let you use dependencies! I havn’t tested on 2013 but should be ok unless they’ve changed the dialog significantly. If you really need define a manual manager ip, the functionality can be added pretty easily, just let me know
Impressive hack… pretty ridiculous from an API point of view to have to press buttons on a dialog…
We’ve just decided to make the move from 2009… not sure why… ha ha… It seems the entire backburner setup has another layer of gunk added…
I’ll give this a go… thanks…
This is a known issue…
Still doesnt work… f*ck.
The workaround is:
1.1 – Use netrender to submit normally, job wont start, that’s “okay”/expected
1.2 – Open Monitor.exe and connect to the Manager
1.3 – Select the job, right click, select Edit Settings
1.4 – Change the Frame Sequence to Frames and click OK
1.5 – Job should start working now.
The problem still persists in the XML creating when submiting thru netrender, thus re-writing the XML by simply changing some parameter on the job, makes Monitor.exe to write a correct XML file.
Hope this helps, cheers.