[kovarex] [0.17.49] Trains repathing in chain sequences still not obeying reserved block restriction sometimes
Posted: Fri Jun 14, 2019 4:48 pm
See 71371
Hate to have to keep bugging (hyuk hyuk) everyone about this issue, but it's not quite fixed. I found another case where trains will ignore the reserved block restriction and go the wrong way. Here is the test setup: It's similar to the last topic in that it has a circuit-controlled train that tries to go through a roundabout to reach its second stop (right stop), but that second stop gets disabled when it enters the roundabout, sending it back to the first stop (left stop). What's different here, is that there's a cargo wagon plugging up the exit block the train needs to get through to get back to its home stop.
If you turn on the constant combinator and send the train off, this happens: It's probably important to note that the train jerks to a stop instantaneously when it needs to repath, and complains about "No path" occasionally once it's stopped in the roundabout. As far as I can tell, these two behaviors correspond to the pathing failing, so I suspect the train state is getting reset somehow.
What's really bizarre, is that if you swap out a rail section so that the upper return path is connected (it doesn't matter if the lower one still is or not), then the train returns to pathing as expected: This is really odd, because it still has to go through the exact same chain block and exit block, but somehow not having to rejoin the roundabout makes it work. Just in case it was some weird pathfinder behavior due to the presence of a loop, I tried breaking the left side of the roundabout circle (between the 2 chain signals), but that didn't change the behavior.
So in summary, there seems to be strange failure of the pathfinder when asked to re-path within a chain sequence, the only paths to reach the new destination go through a reserved exit block at some point (even if there are unreserved blocks available to stop in before that), and some other woo-wah condition that I can't figure out is present.
Test save:
Hate to have to keep bugging (hyuk hyuk) everyone about this issue, but it's not quite fixed. I found another case where trains will ignore the reserved block restriction and go the wrong way. Here is the test setup: It's similar to the last topic in that it has a circuit-controlled train that tries to go through a roundabout to reach its second stop (right stop), but that second stop gets disabled when it enters the roundabout, sending it back to the first stop (left stop). What's different here, is that there's a cargo wagon plugging up the exit block the train needs to get through to get back to its home stop.
If you turn on the constant combinator and send the train off, this happens: It's probably important to note that the train jerks to a stop instantaneously when it needs to repath, and complains about "No path" occasionally once it's stopped in the roundabout. As far as I can tell, these two behaviors correspond to the pathing failing, so I suspect the train state is getting reset somehow.
What's really bizarre, is that if you swap out a rail section so that the upper return path is connected (it doesn't matter if the lower one still is or not), then the train returns to pathing as expected: This is really odd, because it still has to go through the exact same chain block and exit block, but somehow not having to rejoin the roundabout makes it work. Just in case it was some weird pathfinder behavior due to the presence of a loop, I tried breaking the left side of the roundabout circle (between the 2 chain signals), but that didn't change the behavior.
So in summary, there seems to be strange failure of the pathfinder when asked to re-path within a chain sequence, the only paths to reach the new destination go through a reserved exit block at some point (even if there are unreserved blocks available to stop in before that), and some other woo-wah condition that I can't figure out is present.
Test save: