By going too slow. Many authors suggest 1 (mph/kph) but that means AI simulations will just crawl through, plus it can mess with timings (expecting you to crawl through, suggesting the route/scenario builder to compensate elsewhere by expecting you to travel at twice track speed). So in reality it's normal to set up a reasonable speed like 80% but being careful after restrictive signals or over unconfigured switches can cause you to go slower. I tend to be casual with my acceleration and I noticed quite often that certain Go Via instructions tick only after reaching a certain speed. Such as exiting Sparks, I only get the tick when I reach 15 mph, instead of when the loco touches the waypoint.
That's just a mistake the scenario creator made. A player Go Via must always be a Stop At instruction using 1 mph speed (the minimum speed to complete this task). Used for AI, you can control the speed of the trains, they will aim to travel at the exact speed given, useful for debugging in the editor fast forward preview. It might be the author tested the scenario setting up the simulated player speed and forgot to reset it to 1mph before release. Normally for AI you would only wanna use the "Waypoint" function for routing, unless you want to exactly time some events.
Don’t think that scenario on WCML over Shap ever got fixed and sadly as you are running on restricted signal aspects at that point you are unlikely to achieve the required 60MPH. I suspect at the time the scenario was made, waypoints were yet to be a thing or the author needed to use the Go Via to trigger a text message.
No, it's clearly a leftover from scenario testing, because there is no reason to give the player minimum speeds they can't know of. I've fixed it (The usual modified Career "Scenario.bin" error message must be cancelled with F2 and Cancel)
Hey - I knew we've had this before . So my deja-vu feeling was right... https://forums.dovetailgames.com/threads/wcml-over-shap-a-tour-of-scoring-bug.53136/
