after clicking the button, max ui shrink down , and a Network Job Assignment window pops up, for some reason , i want to do some manually tweak here in my submission script.
How do I press the render button by mxs ? mxs script listener show nothing.
There is no way to actually hit the render button using maxscript. But as other people have pointed out, you do have access to the seperate render commands through script. Although I agree that having actual access to hitting the render button would be useful in a number of situations.
- Neil
Type render()
yes but instead of the Network Job Assignment dialog, i got a render window. any other ways ?
if you need to use network rendering, there is a NetRender Interface that you can use. the help is the best way to find out the details of using this, but here is something to get you started –
manager = netrender.getmanager() -- create a netrender interface instance
manager.connect #manual <a string containing the manger computer name or the ip address> --connect to the manager
jobvar = manager.getjobs() -- gets an array of all jobs on the queue
numjobs = jobvar.count -- get the number of jobs
netjobs = for i = 1 to numjobs collect jobvar[i].name -- collect the job names in another array
manager.disconnect()
you can also use the auto connect function instead of the manual to search for the manger by specifying
manager.connect #automatic "255.255.255.0"
you get the idea!
[color=white][/color]
actionMan.executeAction 0 "50031"
Does a Quick Render if that’s what you need.
yes, and there are few really bad things on netrender interface: it’s not possible to set dependecies for jobs and configure sending of 64/32bit jobs.
yes, and there are few really bad things on netrender interface: it’s not possible to set dependecies for jobs and configure sending of 64/32bit jobs.
Ain’t that the truth. i had a strange thing with netrender in Max 8 where I wondered why you cant change the job name on the queue manager. Since there is a parameter in the netrender interface for jobname, i thought id write my own “mini” queue manager. only thing was, each time i changed the job name, it would add the rendered frame range onto the end of the job. so if i was rendering 0-100 frames, i change the name and bingo, it would render 0-100 TWICE! i couldnt find a workaround, including trying things like setting the frame range afterwards. I came to a conclusion that was the reason that Autodesk left it out of the queue manager. any one else noticed this? :shrug: