Absolute game tick/time in performance monitor log thing

[Honktown]

Adding an absolute game time would make it easier to know more precisely when there might have been a performance discrepancy (and could match prints in the log if there were any).

[PyroFire]

realtime is not deterministic and therefore not possible.
You only got game ticks, and you cannot know how long a tick took to render.

In logs - maybe, and i agree this would give us a way to benchmark scripts that is not currently possible.

+1 (log realtime timestamps)

[Honktown]

realtime is not deterministic and therefore not possible.
You only got game ticks, and you cannot know how long a tick took to render.

In logs - maybe, and i agree this would give us a way to benchmark scripts that is not currently possible.

+1 (log realtime timestamps)

Yeah, I'm talking about "factorio-perf" thingies, not anything accessible in-game:

performance log

perf.png (23.58 KiB) Viewed 1480 times

factorio-current

log.png (27.02 KiB) Viewed 1480 times

In factorio-current we get timestamps, but in the performance log there's no tick/timestamp. A name is like: Factorio-perf-01779_20191225-170529<hardware>, from which I can discern the date, and presumably hour, minute, second, but is the first number the tick? I'd have to test, vs having it in a cell in the performance log. (I didn't notice the number sequence in the name before, so this might be kind-of moot).

[PyroFire]

That's the build number. 0.17.79.
And yes the last number is the time in 24 hour time. 170529 = 17h:05m:29s (5pm)

[Honktown]

That's the build number. 0.17.79.
And yes the last number is the time in 24 hour time. 170529 = 17h:05m:29s (5pm)

Hah, clever catch on the version number. That does mean there's no tick-stamp in the log.

[PyroFire]

clever catch on the version number.

No, putting the build number in there like that is fairly typical.
Knowing that comes with experience.