Have a weird situation…I'm creating a scene ‘master control’ HDA that drives a number of parameters via setting environment variables.

A lot of the parameters I'm driving are on a ROP (it's a Redshift ROP but I confirmed the behavior is the same on other ROPs as well).

For instance, I have an operator path parameter on the control node from which a script sets the $CAM_REN environment variable. I can then enter $CAM_REN in the camera field on the ROP and the field accepts it and updates as expected.

When I try to do the same to any parameters that don't have fields–like toggles and ordered menus–via the ‘Edit Expression’ option, the parameters error. They even remain in an error state if I revert to the previous expression value (on/off for toggles, etc).

I'm driving them with relative parameter references instead for the time being, but I don't want them hooked into a specific node.

Anyone know what's happening here?

–
MC

Figured it out…started with string assignments (chs) and in my hurried copying failed to switch to int assignments (ch). And since basically every non-field parameter has a numeric token value, well, things fall down go boom…

–
MC