[2.0.11] Interrupt condition "X is not full" flickering

[Hares]

The Problem
Interrupt for delivery:

10-27-2024, 01-11-02.png (346.96 KiB) Viewed 534 times

All Iron ore / Load trains stops are either disabled or have limit=0 atm.

Then it actually accepts the "devlivery" and immediately aborts it due to the last interrupt

Note the train status: "Destination stop full"

10-27-2024, 01-12-21.png (460.05 KiB) Viewed 534 times

10-27-2024, 01-13-13.png (62.49 KiB) Viewed 534 times

This results in schedule flickering every 5s, as well as train searchlights blinking.

Looks like a bug, or am I missing something?

Context
My own multipurpose train system design, inspired by DocJade's AutoRail

Blueprint for the train with configured interrupts:

0eNrtV1tr2zAU/itBTxvYLE7jdgnrYHRsL30a21MJQrGVRFSWjCynC8X/fedYSuwlbpx0lzIYFFJJ5/qd7xzJj2QuS54boSyZPhKRaFWQ6d0jKcRSMYl7imWcTInUic60FWtOqoAIlfLvZBpVQYeoYUK2hEbVLCBcWWEFd8brxYaqMptzA1aCrWZhQXe5smFtIiC5LkBLKzQOlsIovgrIhkwv4wo979kZ7eygGRUWVuedRuKtkYBAwtZoSed8xdZCGxRKhElKYSlXbC55SqbWlDzYbYNKujO4EKawtIHAbnIMYC2MLRmmsM2slghvifNZWIaID3GR5cwwi67Jezyug6cYfM7T001/JYAJIMhcaOTOC4bu/NqLLWQp0hBdZtxyMxt8wo3Bm8GtZikYzZgCJVoHUVApMmF9nffQvjgV7YlD+wqiS4XhiTt9+x/7BvtvSp6J/jjoaMwjDXNZYQ8iplTqpSisSAr6sBKwzvRaqCWZLpgsAGptBPjymQBIwvLMta1IW02eaOaa3B3DqaJCrUFVm40Tb1ZRDU5y71EvEf94iGl1CkVtoVkFf4cAxOcPjasKJ1GRrHhaSj+KGvRwPW6do/rS6DIHFx9Kq8OvWJTp4IaZpR68isJxGL0mOOWglKbMrTPog3qKASWXbQJ84bjTsrYjuLPmGMqp5x9TSBK/QE2K8NMaLMrUpm2gq0P2atc0Q7zfDe9IPWH/jP9CS+gD1H/JKIxO7rntCCPqCgOYYaHy3Je51evo/LqZgTO30bLeUeYH1h5mJ9Z6UUqIdIahwHQQKac77rk5iVgd55//aTEQqe2Z/YQOptPW+MgltIvZnMdWnuV2Q/qq6ed8XwV7xvF+lr2Dvy+sIueJWIiEphwmp6pLT5W2riQnTP5D3N0Y8dfuC/r3V88Rfj8ro+dQ3LE7ePwN6Zzv3vPzie6q78a/0143EKSEfwfps/oMWXFarzVD8xfb7ecM+pvtXKodIPQP1Hr/Uhh81gOroaa5tucXlEE1PEpB/9XTvGlwWKPDPiq0xwr2IdUGxgvNmV116UIlD7A883o8jPH8MkLE8DGxhlch7onkHlQuhsOjN+TMvQEt3M7oSrnPkW3QGl+fY5R4gC8V3L0bBaPgIhjNZu6pC26bL+aASDaH14N7INalhz3o2aLOPb4cTcaTSTyOxqNRFFXVD4pebtE=

Copy blueprint

[Hares]

More on that: that prevented other signals from triggering the interrupt: copper stops were open by train did not leave the depot. Something's definitely broken. Only Iron ore flickers, others do not. Checked all combinations of enabled=false & limit=0, result is the same.

Edit #1:
Only trains with multiple signals in the depot flicker (screenshot 1)

10-27-2024, 15-14-11.png (358.52 KiB) Viewed 480 times

Trains in depots with only one item signal do not (screenshot 2)

10-27-2024, 15-14-14.png (418.74 KiB) Viewed 480 times

Currently "hotfixed" by adding decider comb providing random signals every tick.

[SRGfroster]

We've had the same issue, so thank you a lot for posting this as it helped us a tremendous amount.
I think what happens is: you supply more than one signal at a time and the interrupt does a check for all signals on the line.
Thus, if you have a request for iron ore, copper ore, stone and coal it will try to allocate 4 trains to it.

But the "signal parameter" will match the first signal that passes the wait conditions and it'll replace the station names. Thus you create a horde of 4 trains heading for coal (whilst you only needed 1) because that's the first signal on the wire.

Maybe not a bug, but definetely not the way you wanted this to work. The selector combinator with a random input perfectly solves this issue as you only pass 1 resource signal at a time onto the interrupt.

[Hares]

Not exactly, all trains were stuck not carrying iron, and iron only. And that blows my mind. It looks like different signals are checked at the the same time, and any of them can satisfy a condition.

[Klonan]

Hello,

Sorry for not seeing this report earlier,
I believe this is the same problem as this other report, the signals mixing together in the condition checking: 117799

[Hares]

Hello,

Sorry for not seeing this report earlier,
I believe this is the same problem as this other report, the signals mixing together in the condition checking: 117799

So, it is safe now to remove selector combinator selecting a random signal each tick?

[Klonan]

Hello,

Sorry for not seeing this report earlier,
I believe this is the same problem as this other report, the signals mixing together in the condition checking: 117799

So, it is safe now to remove selector combinator selecting a random signal each tick?

I believe so, if it causes problems just message here