Train stops sharing the same name with circuit networks all share their train "release" [0.17]

Things that has been reported already before.
PuddlesRex
Manual Inserter
Manual Inserter
Posts: 1
Joined: Mon Mar 04, 2019 8:14 am
Contact:

Train stops sharing the same name with circuit networks all share their train "release" [0.17]

Post by PuddlesRex »

The way my iron, steel, and copper refineries are set up is that the output is eight stops per refinery with the same name. For instance, all eight of the output stations for my iron refinery are called "Iron refinery pickup". Every one of the trains that picks up refinery output is the same length, and their wait condition is only full cargo inventory. I have a simple circuit network for each stop that will disable the stop if there is either a train already present, or there is not enough cargo to fill a train.

The bug only occurs when there are multiple trains at a stop. If any one of the trains fill up (their wait condition is satisfied), all trains at all other stops sharing the same name will seem to meet their wait condition, regardless of whether it is actually met. These trains will begin moving to their next destination as though they have a full cargo inventory. However, the trains get confused, and attempt to route back to a refinery pickup, as their individual wait conditions have not been satisfied. I have not tested this with different wait conditions yet, only "full cargo inventory".

This bug only occurs when I have my circuit network in place, and works as expected when the circuit network is removed. No individual station's circuit network is connected to any other circuit network. This system worked as intended in 0.16. I have removed and re added the circuit network, thinking it was a migration issue with .16 --> .17. This was not the case, as the bug persisted. This is the blueprint string for the circuit network I am using on my stations.

The bug seemed to get a little better when I placed a signal immediately in front of the stop. If the train was kept from moving, it would successfully and immediately arrive at the closest station (the one that it was already at), and resume loading. However, the train would still try to move, as evidenced by sound and animation.

I have not tested renaming the stations, but keeping the same circuit network, due to the logistical nightmare of assigning and reassigning trains to make it still run during testing.
Post Reply

Return to “Duplicates”