Strange issue with system time

[yelworC]

I am running latest version of WinUAE with OS3.2.1.

UAE runs in "full window" mode and auto-hides the window when it looses focus by switchig back to Windows with Alt-Tab. Priority is set to "below normal" and rest of emulation including sound is set to run normal when minimised.

I noticed that Amiga System time starts to run behind real time when I often switch between Windows and UAE or when having UAE minimised for some time. Strange thing is, that battclock has correct time setting in this case and system time is behind. When I run "setclock load" in shell, system time restores back to normal.

I have "synchronise clock" enabled but this only has an effect when I open WinUAE GUI and then close it.

Is it possible to have the same routine triggered when UAE is catching mouse pointer after being minimised?

[yelworC]

Am I the only one with this issue?

[haps]

Would seem so far you indeed do be.

[Toni Wilen]

Misc panel "syncronize clock" sets Amiga clock to host time when WinUAE window gets focus.

Also make sure CIA-A clock source is power supply (="big box Amiga"). VSync will drift slowly.

[yelworC]

CIA-A Clock setting did not fix it.

Maybe it's something related to Windows 11? Really strange that only I seem to have this issue.

[Toni Wilen]

Do you get SETSYSTIME log messages when alt-tabbing? (run winuae from command line with -log parameter).

This message means winuae got focus and executed clock sync. Clock sync requires UAE boot ROM active (=at least some uae device must be active, like directory filesystem, uaehf.device etc..)

[hexaae]

Similar issue: http://eab.abime.net/showthread.php?t=108157

[yelworC]

Originally Posted by Toni Wilen

Do you get SETSYSTIME log messages when alt-tabbing? (run winuae from command line with -log parameter).

This message means winuae got focus and executed clock sync. Clock sync requires UAE boot ROM active (=at least some uae device must be active, like directory filesystem, uaehf.device etc..)

Log shows SIZE_MINIMIZED when window loses focus and is minimized and when going back to the emulation it shows "ShowCursor 0". No SETSYSTIME event is logged.

Boot rom is set to "Original UAE (FS + F0 ROM)"

[hexaae]

@yelworC
Can you test it in Windowed mode if you can reproduce it?
From my tests mentioned above it happens only in fullscreen/fullwindow...

[yelworC]

Originally Posted by hexaae

@yelworC
Can you test it in Windowed mode if you can reproduce it?
From my tests mentioned above it happens only in fullscreen/fullwindow...

I tried this before and it happens in all modes (fullscreen/full window/windowed) when emulation window is hidden.

[hexaae]

Originally Posted by Toni Wilen

Misc panel "syncronize clock" sets Amiga clock to host time when WinUAE window gets focus.

Also make sure CIA-A clock source is power supply (="big box Amiga"). VSync will drift slowly.

Want to try this...
Tony, it's ok changing CIA-A to Power Supply 50Hz even when I run NTSC games then? I mean: that option won't affect NTSC 60Hz native res, and the timing for NTSC games won't be forced to 50Hz (PAL), right?

[Toni Wilen]

Originally Posted by hexaae

Want to try this...
Tony, it's ok changing CIA-A to Power Supply 50Hz even when I run NTSC games then? I mean: that option won't affect NTSC 60Hz native res, and the timing for NTSC games won't be forced to 50Hz (PAL), right?

It should be fine. Games rarely (never?) use CIA-A TOD counter. Vblank interrupt/copper is much easier to use.

btw, 50Hz power supply is not same as vsync even if display is 50Hz. Amiga normal PAL display is 49.92Hz. Interlace is 50Hz but it also isn't 100% exact.

[hexaae]

Today I reproduced my issue (cfg in signature. I just use std Adv. Chipset settings), but noticed this strange thing opening Scout that through identify.library 40.0 (13-Feb-2022) was unable to detect chipset details... Maybe just a bug in Scout/idlib but worth mentioning maybe:



P.S.
The other day testing with Adv. Chipset > CIA-A: Power Supply = 50Hz I WASN'T able to reproduce it, or the be exact I saw a strange thing after resume from Sleep + Hibernation: the titlebar clock I use quickly changed the time, e.g. 22:01, 22:02, 22:03, 22:04... etc. 'till it reached the current Windows time. Weird....

EDIT: never mind. Tried to reproduce this selecting CIA-A but didn't work and time was wrong and didn't change.