Incorrect demo time

[oranje]

Hello, I've noticed some weird defrag behaviour when it comes to saving demos which have a long run time. These are some of my demos which have the wrong filenames.

Actual Time - Filename

11:11:624 - boris_daytime[mdf.vq3]11.11.624(oranje.io).dm_68
114:12:832 - boris_daytime[mdf.vq3]11.12.832(oransje.ukr).dm_68

74:11:824 - vivid[df.vq3]04.17.520(oranje.io).dm_68

187:14:424 - j4n_torture[mdf.vq3]18.14.424(oranje.io).dm_68

I didn't think it was a big deal because you can just rename the file to the proper time, but recently I've encountered another bug. In my vivid demo while it says in the console that my time was 74:11:824, the timer actually resets during the run and shows 04:17:520 as my best time. The tr happens around 69:53 into the run, and 79:35 on the timer.

[demon0r]

There's one solution - don't play these long shitty maps.

Nah, just kidding. But wait, every joke contains a bit of true.

[GlueDrinker]

The tr happens around 69:53 into the run

I had the same problem in my first boris_cab1 run (offline).

[|PsY|Shio]

These maps have 2 things in common,
no vis stage/hints, missing wait -1 on trigger_multiple (Startimer).
So mappers could prolly avoid it with wait -1

[kairos]

These maps have 2 things in common,
no vis stage/hints, missing wait -1 on trigger_multiple (Startimer).
So mappers could prolly avoid it with wait -1

I also had this problem on qportal and wsad-heaven. I don't think it's really a matter of wait -1...

[GlueDrinker]

gnj-fulltorture-easy tested positive as well, also missing wait -1.

I used dfengine 1.08 with DeFRaG 1.91.22 beta, offline.