Is this expected behavior?
Posted: Fri Jun 06, 2025 6:52 am
I have a train that waits until 2 circuit network signals, A, and B, are equal in value. A is the output of a selector combinator which is set to "Count Inputs" with it's input being the train currently being at the stop — ie it counts the number of unique items within the train. B is the output of a decider combinator which checks if each input signal (input from the train) is greater than a constant value, N — it counts the number of unique items that are of a certain stack size. So I'm just checking if each item count within the train is above a certain amount, and to wait if not.
What I'm finding is that for a split second, despite B < A, it will evaluate as true (yet I can see, in the train, B = A despite B < A). It's almost as if there's a slight counting delay from the selector combinator or the decider combinator where it sees both values as equal for a moment until it finishes counting, so it evaluates as true for the train.
As a workaround, I have the train set to wait for 1 second or less to account for this delay.
What I'm finding is that for a split second, despite B < A, it will evaluate as true (yet I can see, in the train, B = A despite B < A). It's almost as if there's a slight counting delay from the selector combinator or the decider combinator where it sees both values as equal for a moment until it finishes counting, so it evaluates as true for the train.
As a workaround, I have the train set to wait for 1 second or less to account for this delay.