WinUAE 4.3.0 beta series

[amilo3438]

Originally Posted by amilo3438

More problems ...

Found some gfx glitches in "Noxious-BeyondBelief" demo after the "wet-window" part and also in part after that! (not happens in Winuae4210)

Testing config: quickstart A1200 4MB Fast + chipset/cycle-exact (full) enabled

It seems to work fine now in the latest "winuae_4300b4" with the same configuration.

One note:
Also work fine in quickstart A1200 + chipset/cycle-exact (full) w/o 4MB fast only if KS3.1 is used! (With KS.3.0 it will stop at cube rotation part.)

EDIT:
Another demo "SHD-Revelation" glitches with KS3.0 but seems fine with KS3.1! (quickstart A1200 + chipset/cycle-exact (full) basic) NO it seems fine! (my mistake)

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Not enough information.
- no logs
- no config
- no information which was last working version

JIT + Video Card Picasso IV:

- Winuae 4.0.0 = Only PAL
- Winuae 4.1.0 = Only PAL
- Winuae 4.2.0 = Only PAL
- Winuae 4.2.0 = Only PAL
- Winuae 4.3.0 All Beta = Crash WinUAE

Attach config and Log

JIT + Video Card UAE Zorro III No problem with all versions

[amilo3438]

Yet another problem ...

The demo "MYSTIC-Vital" after the "lady in sfere" part there is some glitches! (in beta1 does not happens)
The config: quickstart 1200 basic + cycle-exact (full) enabled!

[Toni Wilen]

Originally Posted by Toni Wilen

Some lagless beamracing adjustment testing.

Single slice mode work better now.
Some more stability improvements.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_4300b5.7z
http://www.winuae.net/files/b/winuae64_4300b5.7z

Beta 5:

- Don't map invalid Blizzard 2060 maprom space and crash if board has no RAM installed.
- Added support for new cooked adf variant that can store sector headers: sector header data is appended at the end of normal ADF. Only enabled if ADF file size is exactly (80 to 82) * (512 + 16) * (11 or 22) * 2. Practically useless because almost no program uses sector headers and extended adf can already store them (but only in raw mfm form). GUI create disk image creator won't support it.
- Lagless vsync stability improvements. Current raster line polling removed, replaced with scanline calculation using last vsync time and total scanlines. Raster line polling causes huge GPU driver stalls.
- IVS Trumpcard *.driver to boot ROM automatic conversion didn't support older single hunk driver file versions.

[Toni Wilen]

Originally Posted by amilo3438

Yet another problem ...

It does not matter. There won't be any CPU related changes until more CPU internal information is available (which is quite unlikely).

Originally Posted by AMIGASYSTEM

JIT + Video Card Picasso IV:

Your config is invalid for OS4 ("UAE" Z3 mapping). Crash is probably side-effect that depends on other variables. Perhaps it can be fixed, perhaps not.

[Retroplay]

Originally Posted by Toni Wilen

- Lagless vsync stability improvements. Current raster line polling removed, replaced with scanline calculation using last vsync time and total scanlines. Raster line polling causes huge GPU driver stalls.

Anybody else experiencing major slowdowns in b5 ?

WinUAE 4.3.0b5 crawls to a halt with Fullscreen + lagless VSync (Beamraced) (4).
If I revert back to 4.3.0b4 it's running smooth as butter again.

[DamienD]

Unfortunately I can't test "lagless VSync" as it's never worked for me on my old Windows 7 laptop

[arcanist]

b5 works OK on my Windows 10 / Ryzen 1700 / GTX 1070 system with Fullscreen + Lagless VSync + 4.

[alpine9000]

I tried lagless vsync on a an Alienware m15. With the built in monitor the refresh was slow and jerky. With an external gsync monitor is was silky smooth but everything ran way too fast.

[Retro-Nerd]

It's still a Vsync, you have to set your monitor to 50Hz. Works great here, as before.

[alpine9000]

Originally Posted by Retro-Nerd

It's still a Vsync, you have to set your monitor to 50Hz. Works great here, as before.

Ah right I get it now, I kinda assumed with gsync winuae would set the refresh rate to the desired rate as games do.

[hexaae]

Originally Posted by alpine9000

Ah right I get it now, I kinda assumed with gsync winuae would set the refresh rate to the desired rate as games do.

However...
Not to take anything away from amazing work by Toni in that area, but Fullscreen for Native Modes and your natural G-Sync should be good enough anyway to play with WinUAE...
I honestly didn't ever notice any preceptible annoying input-lag to push me test the lagless modes deeply in WinUAE, and is smooth as hell too with perfect auto-50Hz refresh. I've set NVidia's Fastsync for WinUAE.

My WinUAE cfg: https://hastebin.com/alibuvufow.php

[Toni Wilen]

Originally Posted by Retroplay

Anybody else experiencing major slowdowns in b5 ?

WinUAE 4.3.0b5 crawls to a halt with Fullscreen + lagless VSync (Beamraced) (4).
If I revert back to 4.3.0b4 it's running smooth as butter again.

More information needed. (at least both logs).
Does slices = 1 also work badly?

Originally Posted by alpine9000

Ah right I get it now, I kinda assumed with gsync winuae would set the refresh rate to the desired rate as games do.

VSync still works like vsync, with or without g-sync.

Don't enable vsync to get g-sync = vsync-like behavior without vsync related problems.

Originally Posted by hexaae

However...
Not to take anything away from amazing work by Toni in that area, but Fullscreen for Native Modes and your natural G-Sync should be good enough anyway to play with WinUAE...
I honestly didn't ever notice any preceptible annoying input-lag to push me test the lagless modes deeply in WinUAE, and is smooth as hell too with perfect auto-50Hz refresh. I've set NVidia's Fastsync for WinUAE.

Try pinball dreams with and without lagless vsync. It is almost guaranteed you will feel something being wrong without lagless vsync.

[Retroplay]

Originally Posted by Toni Wilen

More information needed. (at least both logs).
Does slices = 1 also work badly?

Yes, 1 slice has same problem.
I see a lot of pull overflow! 3840 1920 3840 inb5 logs.

b4 logs, where everything works attached just in case.

I'm on latest nVidia 441.20 driver (GTX1080).

[Toni Wilen]

Originally Posted by Retroplay

Yes, 1 slice has same problem.
I see a lot of pull overflow! 3840 1920 3840 inb5 logs.

b4 logs, where everything works attached just in case.

I'm on latest nVidia 441.20 driver (GTX1080).

It probably is Windows 7 (or driver) not really supporting D3DKMTWaitForVerticalBlankEvent properly (I already had comment there that mentions some Win7 related side-effect).

So "fix" is to fall back to old method if win7.

[hexaae]

Originally Posted by Toni Wilen

Try pinball dreams with and without lagless vsync. It is almost guaranteed you will feel something being wrong without lagless vsync.

Tested. I use fastsync, and set WinUAE like this (see also my signature) and is perfectly smooth and synced to 50Hz (or 60Hz when in NTSC) with G-Sync to me, I don't force vsync in WinUAE GUI:



I feel no lag. I'm just saying is very good (smooth and can't feel lag) also with bare g-sync even if lagless is technically better
Vsync only (no g-sync) in comparison is horrible.

[r.cade]

Originally Posted by Toni Wilen

It probably is Windows 7 (or driver) not really supporting D3DKMTWaitForVerticalBlankEvent properly (I already had comment there that mentions some Win7 related side-effect).

So "fix" is to fall back to old method if win7.

This happens to me also on Windows 7 - with a good old GTX 770, anyway. Only 3 more months to go, right? (1/20/20 is EOL).

Why use newest Windows when we're emulating computers from the 80's and 90's?

[lordofchaos]

Originally Posted by Retroplay

Anybody else experiencing major slowdowns in b5 ?

WinUAE 4.3.0b5 crawls to a halt with Fullscreen + lagless VSync (Beamraced) (4).
If I revert back to 4.3.0b4 it's running smooth as butter again.

Interesting. Having the opposite effect for me.

With Beta 5, I can now use up to 24 slices with no tearing or slowdown, and yet with last official release 4.2.1 was only using about 6/7 slices before getting tearing.. Not sure what's causing these diffrences, changes to WinUAE/NVIDIA Drivers/Windows 10?

Info enclosed if needed.

(Windows 10 64bit, GTX 750 TI, Driver 441.20)

[Toni Wilen]

Originally Posted by lordofchaos

Interesting. Having the opposite effect for me.

With Beta 5, I can now use up to 24 slices with no tearing or slowdown, and yet with last official release 4.2.1 was only using about 6/7 slices before getting tearing.. Not sure what's causing these diffrences, changes to WinUAE/NVIDIA Drivers/Windows 10?

Info enclosed if needed.

(Windows 10 64bit, GTX 750 TI, Driver 441.20)

It was almost unusable here before this update. (Windows 10 Insider, 1080Ti)

Lagless vsync assumes specific side-effect that is not guaranteed.