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'm not sure if the wait times at platforms impact the pay for the contract. I have the impression that it is only dependent on the actual travel time.
Regarding the changing waiting time & 2 minutes instead of one: We have an non-reproducible bug report that the buttons start to change the time by increment/decrement of 2 instead of one. But you are addressing a problem with the schedule being modified unintentionally.
It is quite important for us to address this but we will need some additional data - your saved game & Player.log once this happens.
https://steamcommunity.com/app/1124180/discussions/0/3123785722654342594/
Let me explain;
I set up a new contract between three stations. Unfortunately I did not double check if the middle station had a 2 minute wait before the trial. I will try to remember to check this point in future.
After the trial finished there was a 2 minute wait on the middle station, I called up the contract details page before finally accepting the contract and it was visible there.
As I said before possibly there was a 2 minute wait before the trial began, that I can't be certain. Is it possible that the train was early and unintentionally that added an extra minute to the wait time so the departure time was still correct? I fail to see my train being that early, it was literally the next station.
I found this and posted there too;
https://discord.com/channels/429247498016653312/1139267588845744178
I can post the files if you think that helps, where do i do that?
The reason is that during the planning phase you see the approximate stop times against other train stops and you can e.g. delay the departure from some station to prevent conflict in the next station. So I suppose the trial run should respect the timing you saw when you accepted the contract. We can indeed change this aspect easily but then the whole contract configuration before accepting is basically useless.
BTW, there is no negative impact on your reward because stop time does not count. Thank to this, you can easily improve your contracts after you upgrade tracks by just moving the arrivals to earlier time (more precisely, move arrival earlier and then departure later).
By keeping departures, the changes you make do not populate outside the segment you configure.
One drawback is that platform gets occupied for longer time - but not because of changes in schedule, but because of faster tracks. If you are running out of platforms, you should indeed start moving the departures as well, but then the conflict resolution starts to be more complex.
I hope the tools we provide are helpful during these optimizations. We prepare an improved schedule editing view for Update 15.
At least now I can plan for it knowing why it might happen and steps to take to stop it happening rather than try to adjust later. I think I have been blindly setting up contracts without checking if some of the default times could be improved.
Thanks.
After multiple tries I seems to found the "reproducibilty", this bug will mostly occur when I try to adjust timetable of 60(?) minutes or above.
For example, let's say COM-1001 arrived at 08:00, it's 08:05 now and I want to adjust COM-1002 timing to like 09:30 or so, the 2 minute increment would occur.
Sometimes it also happen to trial train that would run within several minutes, but never on recent contracted train
This version is currently the unstable version. I will publish it to general audience today or tomorrow.
It seems to be the fix at least the second situation you describe here:
The first situation does not seem to be related at the first sight.
So please let me know if you are able to reproduce it in 1.15.10 and if you are, please attach also a save & steps to reproduce to streamline the fixing process.