> If I open irush and stop a rendering frame by highlighting the frame
> then clicking the "Done" button, does rush actually kill the render process
> (mayabatch.exe, ray.exe, etc), or does it let the process finish rendering first?
Yes, Rush recursively kills the process before marking it Done.
And by 'kill', I mean it kills the entire process hierarchy;
the perl script, and all its children (the renderer, plus any
child processes the renderer started)
If you right click on the Done button in irush, it should tell you about this:
Change frames to the 'Done' state.
The selected frames are changed to the 'Done' state. Running frames are killed.
Command Line Equivalent: rush -done
Changing a frame's state while it's running will always kill it first; before
it changes to the new state. This means Done/Que/Hold/Fail/etc.
While rush is killing the process, you may catch the frame in the
transitional state of 'Die'. So changing a Run frame to Done will transition
through the states: Run -> Die -> Done, where:
Die -- Killed the process hierarchy, waiting for an exit confirmation from the OS
Done -- Means the process hierarchy was killed successfully.
Under Unix, the processes are killed with 'kill -9' (untrappable kill),
and under Windows, they are killed with a similar mechanism.
The exit code of the process is ignored, and the frame is forced into the
state you specify.
|