Pipeline Hooks¶
Five ways to drive renderStacks from outside its UI - for studio setup, farm integration, and anything that has to hold for everyone rather than for one artist.
- Global user functions - seven global MAXScript functions renderStacks calls around its own events, from
rsUserNetSubmitreplacing the submission handler torsUserPreRenderFnandrsUserPostRenderFn. Includes therstckproperties they can read and the order they run in. - Environment Variables - the variables renderStacks reads for central control, and where the settings folder sits for each 3ds Max version.
- Global Preference Override - driving the Global Settings half of the Preference dialog from
rsSettings.iniinstead of leaving it to each artist. - 3rd party render farm support - what a farm vendor needs in order to support renderStacks:
quasiKrystalLib.msein a startup script folder, and the code that activates a pass. - Global variable -
::rsBlockPostSubmitMsg, which suppresses the messagebox after a submission.