[0.12.29] [Twinsen] Decider Combinator bug with "input count" and backloop

[Neotix]

Decider combinator with backloop and Input count as output, send always 1.
Test setup:



When I set in Constant combinator A=1, i get A=1 and B=1 on output (it should be only A=1).


Even if I add second Constant combinator with B=10 and connect it with decider, i still get A=1 and B=1 on output (it should be A=1 and increment B about 10 every tick).

[Choumiko]

That's behaving as i'd expect it?
The first one you are actually looking at the pole, the combinator itself outputs only the B signal.
Second one is because the combinator takes the input count from the signal you are comparing and not the added values from all inputs

[Neotix]

Adding B=10 into red input cause that I get A=1 and B=11 on output. So still combinator send B=1 on output.
And combinator shouldn't send signal by itself if it have "output count" and that count is null.

[DaveMcW]

Connect all constant combinators with green wires instead of red. This will make it easier to tell signals apart.

[Rseding91]

I believe you're misunderstanding what the setting does.

You've said: "When signal A == 1, output signal B with the count of signal A" which is exactly what it's doing.

"Input Count" is not the input count of signal B but the input count of the input condition which is A which has to be 1 for it to be executed at all.

[Neotix]

I believe you're misunderstanding what the setting does.

You've said: "When signal A == 1, output signal B with the count of signal A" which is exactly what it's doing.

"Input Count" is not the input count of signal B but the input count of the input condition which is A which has to be 1 for it to be executed at all.

Mhm, so it's not a bug, it's feature
In that way to pass throe selected signal value on specific condition, I have to use decider with arithmetic.
BTW. It would be cool if you add option in decider to pass throe selected signal.

[Twinsen]

Not a bug, this is how "Input count" works.
But this change has been also suggested here viewtopic.php?f=5&t=13706

I'm most probably going to change the behavior of "input count" to act(almost) like you described here(and like it's described in the linked topic).
If anyone has any opinion about this, post it here or in the topic.