modifying maya scene file AFTER render job has been queued up

[freedomfries]

Again, Qube newb here...

Some render systems take a 'snapshot' of your submitted render scene and the latter is what is read by the farm as a job to process, so you could technically go back to your working maya scene, edit, save it and submit another job from it, and effectively, you would have two different jobs on the farm, independent of the original content.

It is my understanding that Qube reads my maya scene file as was submitted, and so I should not make changes to it after a render job has been submitted, because workers would load the scene with the changes made (provided the worker picked up a subjob after I saved). Is this correct?

Thanks!

[jburk]

That's correct, it renders the scene as saved.  It was set up this way to avoid having to save out a scenefile every time you submit; some scenefiles can take many minutes to save, which is a pain.

Qube provides the ability to override many of the renderGlobals directly in the submission UI.  At the worker end, the scenefile as saved by the user is loaded up, the job data is consulted for any renderGlobals settings that are specified to be overridden, and the appropriate "setattr renderGlobals...." MEL command is run.  So the scene is modified in memory, not on disk.

This was originally implemented as a way for lighters to submit many render tests from the same file without having to save versions that only differ from each other by one RG setting.