Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Trung giản thể)
繁體中文 (Trung phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bulgaria)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraina)
Báo cáo lỗi dịch thuật








Vehicle restrictions - I have really struggled to re-implement this, because the API allows access to all vehicles and doesn't tell you what restrictions are in place (if any) so I have had to use some different ways to figure out the restrictions and they are not completely robust. I may put in an override in the new config menu.
Depot placement was a big problem early on, it is amazing how often it would end up in completely the wrong place. There is logic that builds the depot along the route as a backup, but this is unreliable like if the line is entirely over water.
Calculating the cost is possible though it requires going through a full build it could be something I implement later as its not totally trivial as it would involve some callbacks and sending the data back to the UI thread.
With line upgrades yes I wanted to have a "double track" option, to automatically do it. Now in the lines report it will suggest double track if the line only has 1 train - this is a performance optimisation so that it doesn't do the work of figuring out if it really is double track until you actually click the "execute" button.