Either I'm misunderstanding something, or the fix in the 0.17.38 patch notes is not working as described:
I threw together a test rig with a roundabout and 3 exits, and told my test locomotive to go to one station (south), then switched to another (north-east) as soon as it entered the roundabout. I expected it to head down the southbound exit, because I thought that the new rule would prevent it from picking the southern leg of the roundabout for its path (since that path consists of only chain signals followed by a reserved block), but it did pick the southern leg, and planted itself in the roundabout. The southern station loops and comes back north, so the expected behavior would have been to exit south (following the old reserved path), loop through the southern station, and wait at the southern entry to the roundabout.FactorioBot wrote: ↑Fri May 10, 2019 2:36 pmChanges
- When a train performs path finding while in a chain signal sequence, the pathfinding will have a constraint to not go through reserved block before exiting the chain sequence. This solves a problem of train intersections being possible to be deadlocked even with proper chain signals usage in cases of using temporary stops or when path is changed because of station is being enabled/disabled by a circuit network. (68681) This also allowed us to to let train recalculate path spontaneously even in chain signal sequence, as it shouldn't break anything now.
My test save is attached.
P.S. I'm really rooting for this fix because it seems like it would solve all the unexpected failure modes of a properly signaled roundabout (including trains crashing into themselves).