FIXED: Using CHOP channels as parameters for a container COMP not working [2021.11180 - Win10]

I want to control the background alpha parameter of a container COMP using the state of a button. To do that I am trying to connect a null CHOP to the output of a button. When the parameters of a container COMP are referencing this null (either by “export chop” or “chop reference”) the parameters are not in sync with the null CHOP. When the button state is changed it seems the container needs to cook (rmb–> force cook, navigating into the container, going to perform mode, …) before the parameters are “correct”. When using a CHOP execute to set the parameters everything works as expected. It’s also working as expected when the parameter is bound to a custom parameter from the top container that is then referencing the null CHOP.

I’m attaching a simple toe file as example.param_chop_reference.toe (4.4 KB)

Hello @Trostomaat and thanks for the report and example file.

I confirm that I can reproduce your issue on my end.

I added an issue to our bug database for a developer to look into it.

Thanks,
Michel

1 Like

This will be fixed in builds 2021.11770 and later :slight_smile:

1 Like

Thank you :slight_smile:

This bug appears when referencing values from DATs as well. @JetXS can you share the schedule for when 2021.11770 will release? I’m teaching a UI workshop in a few weeks and just want to make sure I inform students which version to download

Hello @benjaminben

I can confirm that the fix is also covering the DAT cell reference case as well :slight_smile:

We are hoping to release a new stable build soon!

Thanks,
Michel

2021.12360 is now posted with this fix.