Why do some speed limits not show up in the F4/F3 'route knowledge'?
Even going back to the EA RS demo, there was a 15 limit just after the long curve out of Bath that had no warning on the F3 display; the 25 limit into the left-hand platform arriving in Oxford doesn't show up; and driving the Cajon Pass over the weekend I passed a 45 limit that was displayed in the F4 route diagram, only to find that I was suddenly speeding at 41.5 because the limit was actually 40!
I'm sure it's mostly just a trick to make you actually read the lineside signs, but why just those few locations?
"Hidden" speed limits
Moderator: Moderators
"Hidden" speed limits
i5-4690k | 16 GB | GTX970 | Win 10 64bit | h/k SoundSticks | 1680x1050
- Kromaatikse
- For Quality & Playability
- Posts: 2733
- Joined: Fri Jun 12, 2009 5:39 pm
- Location: Helsinki
Re: "Hidden" speed limits
It generally happens when a sign object *hasn't* been put in - it is this that shows up on the track display. It has to be linked to the track in the correct place, and given the correct speed indication.
Sometimes the signs are wrong (eg. entering York from the north, the sign says 30, the actual limit is 15). Sometimes the signs are missing (eg. Bellshill eastbound) or not linked to the track (the 15mph gantry-sign at Glasgow Central). Sometimes the change in speed limit is a mistake in the track properties (southbound at Durham, the 30mph from the goods loop spilled onto the mainline - but this was fixed recently).
All of those things are best reported to the route author. In many cases this means support@rsc. It can take a long time for fixes to appear, but not reporting them guarantees that fixes will *never* appear.
Sometimes the signs are wrong (eg. entering York from the north, the sign says 30, the actual limit is 15). Sometimes the signs are missing (eg. Bellshill eastbound) or not linked to the track (the 15mph gantry-sign at Glasgow Central). Sometimes the change in speed limit is a mistake in the track properties (southbound at Durham, the 30mph from the goods loop spilled onto the mainline - but this was fixed recently).
All of those things are best reported to the route author. In many cases this means support@rsc. It can take a long time for fixes to appear, but not reporting them guarantees that fixes will *never* appear.
The key to knowledge is not to rely on others to teach you it.