Page 1 of 1

Once more... Decider Combinator and Input Count

Posted: Wed Nov 26, 2025 6:16 pm
by Tillo.Eaux
Hello (:

I ran into unexpected behavior with a multi-condition Decider Combinator and the Input Count Option. My intention was to use the decider to map the capacitor charge C to a color and output both the color signal and C to a separated circuit network for a colored light bar. In the picture/blueprint below you can see how I tried to do it. Note the in- and outputs working as intended, except for the pass-through of C on the red wire, despite the condition (C>50 AND EACH=3) passing. If I switch the C output to R+G, then I get an output of C=3.

So, I am wondering, how does the combinator select, which conditions to take into account for its outputs? Does EACH always override all others? Is that intended behavior?

Thanks for taking a look! (:
11-26-2025, 18-00-57.png
11-26-2025, 18-00-57.png (539.37 KiB) Viewed 115 times

Re: Once more... Decider Combinator and Input Count

Posted: Wed Nov 26, 2025 9:16 pm
by sczsne
i see your problem!

it's the "each = n" statements. when an "each" statement's condition is true, it passes through the value to the "each" on output side. any other signal that does not match that "each" condition will not pass. so, the C signal is eliminated, because anything that isn't , for instance, =1 in the first block of conditions, won't be passed through.

Re: Once more... Decider Combinator and Input Count

Posted: Wed Nov 26, 2025 10:34 pm
by jdrexler75
Indeed, you can have the C signal show up by adding an "Each(R) = C(R)" OR condition at the end. However then the output will be C+1, since you get 1 from the each output as well.