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
Screenshots of the stations (their settings specifically) and possibly one of the map to see where everything is would be very helpful to have a better idea of what is happening (and of what you could do to fix it).
But best you show some screenshots which allows for a more detailed analysis.
I would imagine that the most likely cause of this confusion is that train limits have an effect at a distance - a train 500 miles away can "block" the train station until the train 500 miles away has arrived and finished unloading. This is the correct behaviour (it stops extra trains from blocking the rails if there is only space for 1 train) but possibly not what you want.
You probably should add stacker stations where the trains can go if there are no valid destinations if you don't want them blocking the loading/unloading stations.
That cannot possibly be the case here - if there were a missing rail then the train would flash the "no path" error instead of the "destination full" error.
Likely you are missing a rail somewhere (I would look at the path to the other stations).