That should save all the hassle of forgetting to switch those two options to the right setup The try catch thing is because these changes will not be applied unless the dialog is closed.
'Lighting assignement' section contains three list: Solo light list contains lights that will be only lights turned on during the rendering, 'Forced On' and 'Forced Off' lights are turned on or off respectively during the rendering. I'm working with 3Ds Max 2014, Vray 3.2 and Win7 Ultimate.After all these setting will be set up (if some properties is not set value from the Render Setup will be used), check the camera(s) in the list and hit Render button. Second I have an idea that with "keywords" in your script (for example %scenestate%) you can also use a vray "keywords" for example if you use: D:\Work\%cameraname%_%rendertime%it would be very useful, but I dont know if you have access to this variables, or if it isnt too time consuming to add that. Is the crash happening with an unhandled exception? I got the same issue and fixed it by correcting whatever goes wrong when the second camera loads (another render preset). Please note that I am very much a beginner in Maxscript so I tried as hard as I could.Additional functionality is Lighting Assignment - you can specify which light will be turn on or off for selected camera during the rendering.1.10.3b Fixes: This is major update of the script, so it may not be as stable as before.
This script aims to replace standard 3dsmax's Batch Render and imitates Houdini Output Node workflow.Using it you can specify rendering parameters - frame size, frame number, output path - directly to camera object, so every camera in scene 'knows' what it intended to render.