Page 1 of 1

[2.0.9] "[virtual-signal=signal-item-parameter]" is not read from the interrupt condition for empty trains

Posted: Thu Oct 24, 2024 1:04 pm
by Hares
Setup:
Train schedule:
Train schedule
Train schedule
10-24-2024, 16-05-49.png (48.84 KiB) Viewed 160 times
Interrupts - Minimal setup:
Interrupt Load -> Unload, minimal
Interrupt Load -> Unload, minimal
10-24-2024, 16-00-24.png (42.65 KiB) Viewed 168 times
Interrupt Unload -> Load, minimal
Interrupt Unload -> Load, minimal
10-24-2024, 16-00-45.png (44.61 KiB) Viewed 168 times
Interrupts - Full setup (different load->unload conditions, allow interrupting other interrupts) - in the save file:
Interrupt Load -> Unload, full
Interrupt Load -> Unload, full
10-24-2024, 16-01-25.png (52.52 KiB) Viewed 168 times
Interrupt Unload -> Load, full
Interrupt Unload -> Load, full
10-24-2024, 16-01-41.png (41.81 KiB) Viewed 168 times
Save file attached.

Steps to Reproduce:
  1. Re-create the setup or load the save file (deploy trains to the ore pickup and fill their cargo)
  2. Launch any of the trains by switching them from manual mode to automated
Expected:
  1. Train is launched by the "Load -> Unload" interrupt
  2. When unload is finished, train is sent to the train stop it started from (goes backs and forth between two train stops of the same item type)
Actual:
  1. Train is launched by the "Load -> Unload" interrupt
  2. When unload is finished, train enters manual mode
  3. Train is permanently stopped until manual interference

Re: [2.0.9] "[virtual-signal=signal-item-parameter]" is not read from the interrupt condition for empty trains

Posted: Thu Oct 24, 2024 1:09 pm
by Klonan
Hi,

Thanks for the report,

Unfortunately the generic items dont' work with empty trains in this way, it is a good idea for a future feature

Until then, you can provide a list of all signals with a constant combinator and use that to populate the available signals