Ahh, I understand where I've gone wrong, most of my experience with this sort of thing comes from loading bays and placing spurious signals causes some bizarre pathing that is explained by signal count, but that may be to do with it picking the route that gets the train closest to its (unavailable) destination. It doesn't account for everything though.Loewchen wrote:This is incorrect, the length is the factor, amount of blocks is irrelevant, make a simple setup like...
And I have sat in a train and watched its route change 3-4 times in quick succession as it passed signals. It does recalculate frequently, but I disagree on needing a timer for chain signals. All you need to do is set up an event so that when a signal goes green it notifies any leading chain signals which then trigger a recalculation of any trains in their block.