[2.0.14] Train Interrupt skips a station

[Roaders]

Hi

I have a train route that simply goes between a mining station and a smelting station. I have a train limit of 3 at the smelting station and if the mine is full I have full trains of ore waiting behind an empty train that is waiting to go to the mine (which is blocked by another train being filled).

pic

11-03-2024, 14-17-43.png (116.1 KiB) Viewed 685 times

To fix this I created an interrupt:

pic

11-03-2024, 14-17-26.png (85.4 KiB) Viewed 685 times

If "Destination full or no path" go to station "Holding Area"

The problem with this is that the train leaves the smelting station and holding area station is added after the mine. This means that the train does not stop at the holding area and goes straight from the holding area back to the smelting station with no ore.

IMHO this is a "skip" not an "interrupt" as a station in the sequence is skipped entirely and my trains end up on an infinite loop.

[Klonan]

Hello,

Can you provide the save game?

[Roaders]

save file added

[robot256]

Possibly related: 116454

[supremecool]

I encountered the same issue after coming up with pretty much the same train schedule as what you've shown:

factorio_MQ8Yn4aIub.png (249.67 KiB) Viewed 423 times

The problem in this case is that a train with empty cargo at the dropoff station will attempt to path to the pickup station. If the pickup station is full the interrupt triggers and takes it to the depot. But the interrupt station gets inserted after the pickup station in the schedule, so once the train leaves the depot it is now going to the dropoff with an empty cargo inventory!

You can fix this on a case by case basis by adding an extra station in the interrupt that takes it back to the pickup. However I'm not satisfied with this solution since currently all my trains use the same depot interrupt, so fixing it would require creating a new interrupt for every one of my train groups. An option in the interrupt setup which determines if the interrupt stops are inserted before or after the current stop would resolve this issue in a more general way.

[robot256]

Are you running the latest experimental version? The fix for 115988 might have changed this behavior.

[supremecool]

I wasn't playing on experimental before, but having switched over to it the issue does seem to be resolved

[Loewchen]

115988