Simple Tachograph for ETS2/ATS, v1.7.3

[knox_xss]

I'm sorry, I don't understand where is the problem.

Remember,

After a week's rest, the time of driving for a week is first copied into the driving for the second week, and then resets.

This is as intended, as it should be. According to the AETR rules.

[pero]

I know I kinda described the issue with to much complexity.

It copied the time from weekly drive (of Week 1) to the time of driving for 2 weeks (like it should), but it did not reset the counter for the weekly drive time after that. It kinda missed that the week changed (the time for week change was set to midnight from Sunday to Monday), from Week 1 to Week 2. It kept adding the Week 2 driving time to the driving of Week 1, instead of reseting weekly time to 0. I have had enough resting time for the week (2700 minutes).

Basically, it copied the 1 week drive into the 2 week driving time, but did not reset the week 1 (weekly) drive time to zero.

The more I type, the more complicated my explanation gets. I`ll try to replicate this tomorrow, with log from Tacho and the game.

[knox_xss]

@pero
I make a video for you: https://youtu.be/KfaA8p-_1jY

Explanations step by step:
1) rest time is 0:11, daily and weekly DT (drive time) are 0:06, 2weeks is 42:29
2) I rewind time ahead through console - daily DT resets, rest time is 24:07, weekly DT and 2weeks DT remained the same
3) I sleep through the game first time - rest time is 35:08, daily DT, weekly DT and 2weeks DT are the same
4) I sleep once again - weekly DT resets, because rest time is more than 45 hours, it is 46:09; daily DT remained the same, 2weeks DT become as previous weekly DT
5) I decided to move slightly - new shift time and new week time are changed to current game time (a moment when I moving after rest), daily, weekly and 2weeks DT are increased by the same value (1 game minute).

As you can see, there are no problems here, and never have been.

I`ll try to replicate this tomorrow, with log from Tacho and the game.

It would be nice.

[natvander]

Note that for ATS, while a driver has a 14 hour window in which he can drive, he can only drive a maximum of 11 hours.

So if a driver starts driving at 00:00 and drives continuously (disregarding the mandatory short break), he can only drive until 11:00. If he makes stops along the way, he can only drive until either the 11 hours driving is up, or until 14:00 (which ever comes first).

[pero]

Oh wait, the new week time is supposed to be start time of the current week, not the start of the 2nd week? That was the thing that was bothering me, I thought it is the time entry for the start of week 2.

[Jarog02]

Hello
I have a small problem with the hotkey to display the F12 key, I do not know why, but this function does not work for me.
I have included uset g_developer "1" uset g_console "1".

I get a notification in the console 1 hour 20 minutes before the end of the working day, but I can not call F12 all the information about the tachograph. I have to go back to the desktop to get a look at the full information.
Have you met with such a problem?

[natvander]

Have you opened the console before/after tapping F12?

[knox_xss]

@Jarog02
Make sure the file config.cfg contains this line:

Code: Select all

hotkey_tacho=[123]

Or try to set different key - in the program press "Hotkey config" button, press desired key, then press "Show tachograph info" button to save the key (or key combination).

Oh wait, the new week time is supposed to be start time of the current week, not the start of the 2nd week?

Exactly. "New week time" is the time when you start new working week after weekly rest. It is recorded not directly at the end of the rest, but at the beginning of the movement after the rest. The same is for "New shift time" (after daily rest).

[pero]

I think I understand how this part of it should work, thanks for clarifying that.

[Jarog02]

- The config.cfg file from your modification contains the following line: hotkey_tacho = [123]
- Changing the shortcut key does not give anything.
- I opened the console before and after F12 (Does it matter?)