Options:
the Script needs to be either:
- Defined somewhere in the plugins or startup on all machines
- Coded directly in a string
- Filein script from any location…
Note:
The script option in the render Dialog actually “sends” the current script along with the submittal.
filein style: from shared folder on Baja server
callbacks.addScript #postRenderFrame "filein \"\\\\Baja\\ScriptBin\\Runme.ms\" " id:#RunMe persistent:true
I guess this is really option 2 and 3 together…
Yup, that’s what I figured. It would be fine if I were trying to make a script for my studio and had control over the way the scripts are installed, but it won’t be fine for this particular application. I’ll find another way to deal with the issue, thanks for all your help.
- Neil
Just to close off this thread, I’ve decided that I’m going to use a totally different approach to dealing with this problem.
The main issue I have is that the script I want to run before rendertime relies on a number of variables that are resident in memory, and selections, etc. That’s why I would have prefered to have the script work after you hit the render button, and before it brought up the netrender dialog, and before it is opened by the slave. To get around this, I’d probably have to find a good way to bake out these variables into something concrete that the render slaves can access and process (like little ini files or something), which is always a possability, but it seems like trying to fix a hangnail with a jackhammer.
I’m gonna sit down and rethink my intended workflow and find a more elegant way to have the same final result without writing out tons of extra script files that the renderslave will have to find and run. Thank you to everyone for all the suggestions, I really appreciate them.
- Neil
Have you considered a custom attribute block on something like the scene node / root trackview / something?
Hey Neil, if you think ini files would help you out with your problem, maybe user props is what you’re looking for. Similar to an ini file but stored on the nodes. Look up “Node User-Defined Properties and Methods”.
Are you writting your own submittal script? That would allow you to do whatever at that time between the user pressing the render button and it going off to Backburner… it also allows you to clean up after the submittal goes, without callbacks…
Examples in Interface:NetRender have everything needed to tackle it that way…
Apologies for bringing up an old thread but the network submittal scripts caught my attention. Is it possible to alter xrefs through this method? Up to now i have been relying on callbacks to do this.