setting Environment pane variable, and invoking a utility programmatically
The updated version of "Mask and Multipass Render Toolbox" now consistently leaves the backdrop visible in the render, though it didn't before letting it update. So I have a question (and a second question for extra credit if it's possible).
1. What is the DAZ Script variable or code to set the Environment pane's "visible in render" value? (It's quicker to run a code snippet than to open the pane and change it back after each run of the utility.)
2. (for extra credit!) The "Mask and Multipass Render Toolbox" has a dialog box that opens to select nodes and to select the type of mask (eg Selected Nodes). Is there a way to programmatically call the utility and specify the selected nodes (for a run of images, it might be the same three nodes for all images run) and the Mask type (95% of the time I use "Selected Nodes")? It's an amazing utility of DraagonStorm's, but it would be even better if I could run a code snippet to invoke it.
Thanks in advance for any help!
--John

Comments
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/object_index/scene_dz#a_1ab5a8b6994eff61ae3622f83c7a1bf934 will get you the backdrop, which then has a method to get the visible in render control http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/object_index/backdrop_dz#a_1a60872ed6f7bfc656a1942fa2ec4eed3f on which you could set the value.
I don't have the product but if it has some kind of scene hierarchy panel the author must have created it - I don't believe there is a built-in feature, though it is easy enough to get the node list from DzScene http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/object_index/scene_dz#a_1a7adc6781427377f21f154cd9bee5ebe2
Thank you, Richard! You are your usual awesome, sir.
The code snippet I ended up with, for anyone with a similar issue, looks like this:
Scene.getBackdrop().getVisibleInRenderControl().setBoolValue( false )
I would suggest, even for a snippet, breaking that down and giving it some error checking - I think most steps would be safe for now, but that isn't necesarily guaranteed for the future.