WinUAE 4.0.0 beta series

[Toni Wilen]

Originally Posted by ED-209

Toni I just want to report on-the-fly switching still results in a freeze.
Though it could be pointless information as I'm not sure anything has changed yet in last 2 betas

I only made some modifications that should make debugging this problem easier. Please attach dump file from latest beta. Actually, attach 3 dump files. There may be some differences.

[vagrant]

Done, here's 3 dumps, all identical steps to reproduce crash; disable jit, launch config, launch game (fastest possible-->CE), quit game (CE-->fastest possible) = freeze.

dump1
dump2
dump3

[Toni Wilen]

Originally Posted by ED-209

Done, here's 3 dumps, all identical steps to reproduce crash; disable jit, launch config, launch game (fastest possible-->CE), quit game (CE-->fastest possible) = freeze.

I found another possibility, not really directly related to lagless vsync. winuae.7z updated.

Also, if it still hangs, does it recover if you wait about 10 minutes?

[vagrant]

Unfortunately no, it still behaves exactly the same & no recovery after waiting 20 minutes.
I went back through the betas to observe exactly how each affect my system;
beta1 - on-the-fly switching works fine, though lagless very buggy with tearing
beta2 - crashes when launching emulation
beta3 - freezes when switching to cycle-exact mode from fastest possible
beta4 - crash & exit when switching from cycle-exact to fastest possible
beta5 - same as beta4
beta6+ - freezes when switching from cycle-exact to fastest possible

[vagrant]

Toni I think the problem is something related with my HDF's.. the same HDF's I've been using for years.
I have 2, one boot partition, and a storage partition with games etc.
I copied both partitions to separate PC directories and changed my config to use these instead of the HDF files and on-the-fly switching is working 100%!

[Toni Wilen]

I am now sure I found the real reason, there is timing possible timing issue when switching modes where different parts of emulation have different idea of current mode. ("tell me when vblank happens, please". "vblank? in this mode? It makes no sense")

Don't "fix" your HDF!

[vagrant]

Great, don't worry I'll keep the HDF's & config unaltered

[Toni Wilen]

Another attempt. winuae.7z updated. (Double check that exe is newer than previous)

[Toni Wilen]

Originally Posted by freddy

Toni, can you activate the string for translation ?

Done.

[vagrant]

Fixed now Toni, working like a charm

[freddy]

Originally Posted by freddy Toni, can you activate the string for translation ?

Originally Posted by Toni Wilen

Done.

Toni, strings of caracters are not active in Genlock and Misc

[Toni Wilen]

Originally Posted by freddy

Toni, strings of caracters are not active in Genlock and Misc

Genlock options fixed but others should already work.

Originally Posted by ED-209

Fixed now Toni, working like a charm

Yay, finally

[freddy]

Originally Posted by Toni Wilen

Genlock options fixed but others should already work.

[jotd]

Toni, found some gfx issue:

Boot up last beta9 in Picasso 96 mode, then enter built-in HRTMon, and exit: display remains gray.

With v3 it doesn't happen (just tested twice in a row with both versions)

[Toni Wilen]

http://www.winuae.net/files/b/winuae_4000b10.7z
http://www.winuae.net/files/b/winuae64_4000b10.7z

Beta 10:

- Full-window mode captured mouse (and moved it to center of screen) even when window didn't have focus.
- Removed single buffer display option, it was only useful when using old low latency vsync mode.
- Help button now asks for opening online help version if help file is not installed. (not finished yet)
- Added windowed mode resize enable/disable option. Default is enabled.
- Added D3D11 standard vsync black frame insertion support. (100Hz/120Hz)
- Action Replay II/III statefile support improved. (For example AR state was invalid when loading AR statefile when AR was already active)
- On the fly switching between fastest possible <> non-fastest possible CPU modes in lagless vsync caused hang in certain situations.
- Debugger: show number of cycles used when tracing (t, z, breakpoints). Only shown if max 2 frames since last debugger activation. (TODO: should also count number of memory accesses and no-wait state minimum cycle count)
- Freezer cartridge automatic RTG switch on/off wasn't reliable.
- Removed forgotten, useless and obsolete "The selected screen mode can't be displayed in a window, because.." check.
- 68030 MMU PLOAD R variant (R/W bit=1) caused f-line exception.
- Clear both ping-pong buffers when pausing/unpausing WASAPI exclusive sound mode.

[mark_k]

Is there any chance the old low-latency vsync option can be resurrected? Lagless vsync is not really useable for non-landscape desktop orientations. [It's kind-of useable with one slice, but there's a glitch region towards the right edge if the Amiga display occupies the whole screen width.] Standard vsync does look OK but that always uses 100% CPU.

[Toni Wilen]

No. Totally wrong way to do it when there is very simple solution: explain the problem in 1 slice and it gets fixed!
EDIT: including photos.

[Rotareneg]

With winuae64.exe 4000b10:

Start WinUAE using A500 quickstart config (no floppy required) set to full-screen mode. Pause emulation and open WinUAE UI with F12. Press "OK" to close UI. The UI will close but winuae will not switch back to the emulation. Winuae64.exe task doesn't close either, just sits quietly doing apparently nothing.

*correction*

I just noticed that WinUAE is actually still in the system tray (I didn't see it before because Windows 10 decided to hide it by default.) If I click on the tray icon the screen flashes black for an instant and then back to the desktop with the WinUAE UI open again. If I hit OK it disappears again. If I very quickly hit pause during the short instant the screen is black the UI will pop up again, but then properly return to the running emulation after hitting OK.

Logs attached, I can send you a manually forced dump as well if you need one.

[PeterK]

Just click "Pause" again and the emulation continues, at least on my system.

[Rotareneg]

There's no window or screen remaining to interact with, and the focus reverts to the window that I launched winuae from.

I just noticed that WinUAE is actually still in the system tray (I didn't see it before because Windows 10 decided to hide it by default.) If I click on the tray icon the screen flashes black for an instant and then back to the desktop with the WinUAE UI open again. If I hit OK it disappears again. If I very quickly hit pause during the short instant the screen is black the UI will pop up again, but then properly return to the running emulation after hitting OK.