It would appear that the routing engine does not take into account the speed that it can travel. I setup two terminals fairly far apart and gave two alternat routes coming out of the station signal:
- A long sweeping curve that is less direct but according to the tooltip will allow up to 200mph
- A more direct route of zig-zagging 20mph curves
It chose to go the most direct route down the zig zags... Just to confirm that the long sweeping curve was in fact faster despite the extra mileage, I did a few time trials back and forth on the zig zag, then deleted a segment of track from the zig zag and timed how long the train took to go the "long" way.
The "long" way averaged around 20 seconds.. the "short" way took about 50-55 seconds each trip.
Now I know this example is extreme... and I don't think the routing engine would always choose the best scenario anyways because even if it DID choose the fastest route I can imagine times where I want one high priority mail train to use the fast track, while I want a freighgt train to take the slower route to avoid deadlocks.
I'm not bringing this up to be a pain, but mainly to reinforce the need for more control of our trains routes... it's one thing to setup a good rail network, it's another thing to allow the computer to use it however it wants, it takes a human sometimes to manage the rails...