You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note:
Section & signal speed limits are displayed in the F10 debug window in km/h
These possibly ought to be changed, although I'm in two minds about this, as speeds in the routefile are in km/h, and this screen isn't really for driving use,
Another case are overspeed messages, which also are always in km/h, regardless of the route setting.
I understand your concern about the F10 debug window; still, I imagine it can be useful to route developers to have that indication in the route specific speed unit. What about having both km/h and mph (one reported from route data and the other computed), at least for mph routes?
Custom speed units can now be set via Route.DisplaySpeed but these are not reflected in the review screen.
Requires changing.
The text was updated successfully, but these errors were encountered: