Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The calculation should be able to calculate most situations, and you can add/remove waypoints manually, but only those.
One thing I have seen it struggle with, are the bypass tracks you mention. It has to do with if the track through station is shorter or not. The station bypassing/stopping is not penalized enough in the calculation I think.
The new calculation takes built track and track speeds into account as well as length. If there is a direct route between two stations in the bottom bar it should be chosen regardless of length. If not the route is calculated and stations enroute added.
The scenario you encounter could be interesting to devs though, to see if they can improve on the calculation algorithm.
Internal ticket: https://bitrich.youtrack.cloud/issue/RR-3748/Add-waypoint-outside-station-to-contract-schedule