======================
Proton: 1588276332 proton-5.0-7
SteamGameId: 365960
Command: ['blahblah/.local/share/Steam/steamapps/common/rFactor 2/Launcher/Launch rFactor.exe']
Options: {'forcelgadd'}
======================
lines omitted
1298812.468002c:trace:module:load_builtin_callback loaded ntdll.dll 0x15d60 0x7bc20000
Hi,
If I take the 1588276332 above as a unix epoch time and add 1298812 seconds to it, I get a date 3 days in the future. What am I missing here?
Thank you,
Help needed to work out the timestamp in WINEDEBUG log
Re: Help needed to work out the timestamp in WINEDEBUG log
It appears timestamp uses your box's uptime. 'cat /proc/uptime' should be similar.
Re: Help needed to work out the timestamp in WINEDEBUG log
Thank you. Do you happen to know if there is a way to make it display the time another way?
Re: Help needed to work out the timestamp in WINEDEBUG log
It doesn't look like it, no. Well, short of hacking it to do something else anyway.
Re: Help needed to work out the timestamp in WINEDEBUG log
Or you could check /proc/uptime when you start wine then run the log through a script and subtract it from each timestamp (or however else you want). That way wouldn't require hacking and building wine yourself.
Re: Help needed to work out the timestamp in WINEDEBUG log
Yes that worked alright. A little cumbersome but workable. Thanks agian.