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
Can I have an option to maintain certain time zone I choose globally when editing timetables?
And shows the fixed time I choose and current local time on top info bar?
Having the ability to tie all of your scheduling (if not the game time), to a given time zone would be really useful.
Same for the train system for the whole country.
Also like Spain is within 0GMT time zone but using +1 for whole country, a fixed time zone setting for creating new train timetables is useful.
If so I will stick with the wrong time zone. That's much better than an offset between train time and local time at the position of the map window. Best would however still be correct time zones.
How can I tell which station is in which time zone?
Is a possible "easy" fix to be able to specify the time zone of each station to solve the time zone issue? (as opposed to split the map into custom buitl time zones based on country borders and such). And be able to mass edit i.e. select a bunch of stations and set the time zone to what you want, so you can change all your network to what you think is the right time zone. I am putting easy into quotation marks because when this is done, if not done properly, timetables may be disrupted.
Seems 12 year old me was lucky when stretching the country from 7.18°W to 4.88°E
Even if you place the station into the correct time zone, the issue will probably remain that the plainly longitude based clock will show the wrong time.
Plus it is a dynamic process with changes from time to time, so real data would always have the risk of outdating and requiring updates. And finally, if now real time zones were introduced what would happen to existing gamesaves? The next case of writing all schedules new from scratch?
So maybe the current compromise, as unconvenient it may be in some cases, is not that bad at all.
Being able to set up custom time zones for individual stations will probably be good for everyone else, if you can bulk-edit them. This would also be easy for software update compared to drawingt actual time zones on the map, which is tedious and can change in real life on a regular basis.
(The only reason I can think about time zone settings for individual stations is those country has multiple time zone and also using daylight saving time)
Yes that's why I said 90% should be good with the ability to set a single time zone.
The level of effort should not be high if bulk-editing is possible - select large areas of track and then use one button click to convert all stations inside the selection into the desired time zone. You may need to do it a few times if the network is large, but it should be feasible to do everything in less than half an hour. Especially if by default each station is assigned a geographical time zone, which will be accurate probably 80% of the time. This is likely easier than trying to program time zones into the code, because then you need to introduce administrative borders which currently are not included, and time zones can also change over time.
The reason I think it's a helpful option is because when you operate across more than 2 time zones, traffic starts being affected by the time of the day patterns. I will use airplane travel for easier illustation. LA to NYC is about 5-6 hours flight plus or minus 3 hours time change. So you arrive into a time that is either 8-9 hours later or 2-3 hours later from the time you departed. One can be rush hour, and the other not. So you probably want to build a timetable taking time of the day into account.
DST should not be relevant because the game is for one week only, hopefully everyone can pick a week that does not include a shift from winter to summer time.