Bug: [Submitter] RenderSetupIncludeLights job parameter is inaccurate if the corresponding option variable is not set

[jericht]

Describe the bug

The RenderSetupIncludeLights job parameter in the job bundle generated by the submitter is inaccurate if the corresponding option variable is not set. The current implementation uses the optionVar MEL command to check if the renderSetup_includeAllLights option variable is set, however if this variable is not set (e.g. by explicitly interacting with the Render Setup editor menu > Options > "Include all lights in each render layer by default" checkbox), the submitter will always report the option to be false, even if the checkbox is checked in Maya. This causes confusion when local renders include all lights, but renders on Deadline Cloud do not.

Expected Behaviour

RenderSetupIncludeLights in the generated job bundle should match the Render Setup editor menu > Options > "Include all lights in each render layer by default" checkbox state

Current Behaviour

It does not match the state if the renderSetup_includeAllLights option variable is not defined.

Reproduction Steps

1. Open an empty Maya scene
2. In the Render Setup editor menu > Options > "Include all lights in each render layer by default", make sure the option is checked
3. In the MEL prompt, make sure the renderSetup_includeAllLights option variable is removed by running optionVar -remove renderSetup_includeAllLights
4. Double check that the Render Setup editor menu > Options > "Include all lights in each render layer by default" is still checked (do not touch it, this will set the option variable again)
5. Double double check, in the MEL prompt, make sure the renderSetup_includeAllLights option variable does not exist by running optionVar -ex renderSetup_includeAllLights. It should return 0
6. Open the Deadline Cloud submitter and export the job bundle
7. Open the job bundle's parameter_values.yaml file and verify that the RenderSetupIncludeLights option is false, which does not match the checkbox value in Maya

Environment

At minimum:

1. Operating system: All
2. Version of Maya: 2024
   3: Version of this package: 0.14.4
3. If this is from a version installed by the Deadline Cloud Submitter installer, then what version of the submitter installer?
   • Not in my testing (macOS), but it will also happen in that case

Please share other details about your environment that you think might be relevant to reproducing the bug.