FIXED: 2022.22400 Can't read custom parameters on Engine COMP

Bugs
,
1

Hey!

In the new version I cannot read custom parameters in the Parameter DAT&CHOP from the Engine COMP, it does work with a e.g. Base though. They do show up when I turn on “Built-In” but I can’t use them this way. Also, they are not working in Python expressions such as len ( engineOP.customPars ). Please fix this, thanks!

P.S. Love the new option to sort them :slight_smile:

Edit: Basically the custom pars are taken as Built-In pars

1 Like
2

Hey @elekktronaut

Thanks for the report.

I’ve logged this as an issue for a developer to look into it.

Best,
Michel

3

I have kinda similar problem, I was able to reproduce it in the clean project:
engine_test.zip (11.6 KB)

So, I have a dmxoutCHOP that sits in the baseCOMP with one button exposed as a parameter. The button turns dmxoutCHOP active parameter on and off. I fire up wireshark and I can see an expected behaviour: when the button is on there is broadcast artnet traffic on the net, when it’s disabled there is no traffic…

Same thing is put into an engine comp. The behaviour is the same, everything works…

Now we take this Active button on the engine comp and put a reference to an external button in it. So the idea is to control enabling/disabling dmx from some ui element. Now it doesn’t work anymore. You can see that the parameter state changes according to the button state, but there’s no more traffic on the network, so the command never reaches dmxoutCHOP parameter. (or if it was in the “on”:state previously then you will see that the artnet traffic would keep getting sent)
If you put the same button reference to the parameter of the baseCOMP then it works as expected, so it’s something engineCOMP specific.

Hope it helps

1 Like
4

Hey @densi

I think this is unrelated as @elekktronaut is mentioning Parameter CHOPs / DATs outside of the Engine COMP, not showing the “custom” parameters when the custom toggle is on. We know why this is occurring and we are currently discussing a solution.

Regarding your issue @densi - I tracked it down (maybe you want to confirm) to the parameter state not propagating within the engine if the parameter wasn’t clicked manually. The issue seems to be present in 2021.10k as well.

I logged an issue for a developer to look into it.

Best,
Michel

5

hm, weird, I haven’t seen this before. But I’m glad that we were able to narrow down the problem. Thank you!

6

@elekktronaut

This issue will be fixed in the next release.

Best,
Michel

1 Like
7

Build 2022.26590 is now available with this fix.

1 Like