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
i fixed it, i rebuild the rails i ve build with blueprints then it is fixed.
[Edit: or tracks :) see below .. ]
The only thing that comes to mind is overlapping but disconnected tracks. I sometimes draw tracks so quick on terrain that they sometimes get overlapped but not connected and sometimes dont even notice I did it. Although this happens only rarely. For the OP to have the problem they describe it would have to be made this mistake at each and every segment along the way and even I couldnt do it that often even if I wanted to.
This is it, rails built by building blueprints do not connect to existing rails no matter how perfectly the rails align and look connected, you have to manually connect them segments (not using a blueprint), otherwise the train will stop where the rails visually touch/overlap but are not joined.
now it makes sense why you keep having this issue all the way down your line.
the best I can suggest is a blueprint that setups the foundation for the rail and one end of it but leave the other end for you to fill in later to connect to the next blueprint.
its just how blueprints work. nothing in one blueprint will auto connect to something in another blueprint even if they line up perfectly.
blueprints dont snap to each other or to other parts, you have to recreate the rail if you want it to snap to the blueprint.