WinUAE 4.0.0 beta series

[Toni Wilen]

Originally Posted by mcbpete

Apologies for not knowing this: is winuaelog.txt different from winuaebootlog.txt ?

Attached is the latter (LLBootlog.txt being 'Low Latency VSync' and LLVSBootlog.txt being 'Low Latency VS 50/60Hz')

If winuaelog.txt is different how do I create this ? (is there a command line switch I enable?)

It is different. Only created when misc panel log option is ticked.

Originally Posted by Mclane

Toni, I just downloaded the winuae2 file about 3 mins ago and whatever you have done the low vysync now works. The only odd thing is that on an A500 config the cpu on screen is show roughly 80%, way way higher than normal.

Same config as I sent you previously as noted as the 'modified one' where cycle exact, freq for monitor set, FS and low vsync being the only changes to a normal inbuilt cfg.

Compared to "old" low latency vsync? Reducing number of slices should decrease CPU usage.

[Mclane]

Ah ok, thanks for getting it going...

Sorry about the messy reports, lot going on here...

Oh silly thing that happened, I hit the prntscreen key before saving the screen via winuae and not only did it muck up the display by making both screens I use amalgamate but the speed Winuae was playing doubled to 120fps. Obviously its not really a winuae and if I hit F12 and start it corrected the display but its odd.

one last question, I didn't read the thread about this new vsync, does dropping the number of slices have any bad effect?

I've dropped it to one and the cpu has on the game I'm playing gone to roughly 50%, I think it sounds ok (low volume)

[mcbpete]

Originally Posted by Toni Wilen

It is different. Only created when misc panel log option is ticked.

Apologies, thought so .... Let's try this again

winuaelogLL.txt is the Low Latency VSync mode
winuaelogLL5060.txt is the Low Latency VS 50/60 mode

EDIT: Aha - I think I've found an interesting line in the winuaelogLL5060.txt file:

refresh rate changed to 50p but no matching screenmode found, vsync disabled

So in the VS 50/60 version it just disables the vsync as it can't run in that mode, so I'm guessing in just falls back to the regular non-Low Latency mode ? (hence the vast difference in CPU usage)

[Amiga68k]

Originally Posted by Toni Wilen

Does anyone have new low latency vsync hang if Windows version is 8 or newer? So far it seems to be Windows 7 only.

Windows 10 here, instant hang with Beta 2. Beta 1 was ok.

[Mclane]

See if http://www.winuae.net/files/b/winuae2.7z

Fixes it for you....Did for me on Win 7, maybe on Win 10 as well?

[Amiga68k]

Originally Posted by Mclane

See if http://www.winuae.net/files/b/winuae2.7z

Fixes it for you....Did for me on Win 7, maybe on Win 10 as well?

Nope, same instant crash

[Mclane]

Weird issues...Hope it gets fixed for all soon..

[Toni Wilen]

Originally Posted by Amiga68k

Windows 10 here, instant hang with Beta 2. Beta 1 was ok.

http://www.winuae.net/files/b/winuae.7z should fix it now.

[Amiga68k]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.7z should fix it now.

Confirmed

[Retro-Nerd]

Originally Posted by Mclane

The only odd thing is that on an A500 config the cpu on screen is show roughly 80%, way way higher than normal.

I noticed this too. With lagless Vsync enabled the CPU usage is app. 50-60% higher than before it was implemented, with default 4 slices.

[Viceroy]

Not sure if this is already noted but I have a system with 3 HDF drives and 1 drive as a dir, when using latest beta 2 the Dir drive is shown as a ndos drive, if I go back to last stable Winuae the dir drive is fine?

[Toni Wilen]

Originally Posted by Viceroy

Not sure if this is already noted but I have a system with 3 HDF drives and 1 drive as a dir, when using latest beta 2 the Dir drive is shown as a ndos drive, if I got back to last stable Winuae the dir drive is fine?

Which WB and KS version? Which program reports it as nodos? (c:info?)

[Viceroy]

KS ROM v3.0 (A1200) rev 39.106 (512k) [391523-01/391524-01]
Workbench 3.01

[Mclane]

Originally Posted by Retro-Nerd

I noticed this too. With lagless Vsync enabled the CPU usage is app. 50-60% higher than before it was implemented, with default 4 slices.

I dropped it down to 1 & 2 slices as suggested by Toni and the CPU gets better but I'm wondering if there's a determent to using less slices (otherwise why have a default of 4).

I'm guessing that its to balance out lower end systems, mines in the old but not ancient slot, I guess higher cpu usage is the payoff for almost no lag in Vsync.

@Damien, all working for you?

PS, clear out some of your PM's I can't reply to the update pack post

[Toni Wilen]

Originally Posted by Viceroy

KS ROM v3.0 (A1200) rev 39.106 (512k) [391523-01/391524-01]
Workbench 3.01

How does it report nodos? How large is your directory harddrive partition? (Windows partition, not what Amiga sees)

I did some changes to how directory harddrive reports size and dostype but it should not have made any visible changes (except to work around WB free disk space wraparound)

Originally Posted by Retro-Nerd

I noticed this too. With lagless Vsync enabled the CPU usage is app. 50-60% higher than before it was implemented, with default 4 slices.

CPU usage is lower when using feature that isn't yet implemented?

As I already, said, does 1 slice equal (about) old low latency vsync? CPU usage can be lowered a bit more but stability comes first.

Final defaults are not yet chosen. 3-5 most likely.

[Viceroy]

Which WB and KS version? Which program reports it as nodos? (c:info?)[/QUOTE]

https://drive.google.com/open?id=1Wb...qhPvu18LM6xf-1

https://drive.google.com/open?id=1Yw...p1bxb31wz7St1t

First one new beta, 2nd image last stable build

The ndos partion is a folder on PC which is my DH1:

[Leandro Jardim]

Originally Posted by Toni Wilen

CPU usage is lower when using feature that isn't yet implemented?

As I already, said, does 1 slice equal (about) old low latency vsync? CPU usage can be lowered a bit more but stability comes first.

Final defaults are not yet chosen. 3-5 most likely.

Good to know!

With beta 2 I get constant tearing over the screen with 2 slices and up. Seems the update helped mainly to fix tearing with one slice, though. In this mode it works much better now.

And the update fixed also the the bug with "Native resolution" on my PC.

Below are the logs for my machine, if it helps with your progress.

[Retro-Nerd]

CPU usage is lower when using feature that isn't yet implemented?

As I already, said, does 1 slice equal (about) old low latency vsync? CPU usage can be lowered a bit more but stability comes first.

Final defaults are not yet chosen. 3-5 most likely.

Actually it's much more than 50%. Very strange. Disabled all filters too.

With lagless Vsync, 1 slice




Without Vsync,



eh: Ah, OK. Had the 2x multiplier (what was it, prescale?) enabled. But still 20-25% with one slice against 5-15% without Vsync.

[Toni Wilen]

https://drive.google.com/open?id=1Wb...qhPvu18LM6xf-1

https://drive.google.com/open?id=1Yw...p1bxb31wz7St1t

First one new beta, 2nd image last stable build

The ndos partion is a folder on PC which is my DH1:

I can't duplicate.. What does C:Info return? Whats the size of PC partition? Does the drive still work normally?

[Toni Wilen]

Originally Posted by Leandro Jardim

Good to know!

With beta 2 I get constant tearing over the screen with 2 slices and up. Seems the update helped mainly to fix tearing with one slice, though. In this mode it works much better now.

And the update fixed also the the bug with "Native resolution" on my PC.

Below are the logs for my machine, if it helps with your progress.

Your config works fine here and looks correct. How does debug color bars look? (end+f9) This must be always mentioned when testing low latency stuff!

Originally Posted by Retro-Nerd

Actually it's much more than 50%. Very strange. Disabled all filters too.

With lagless Vsync, 1 slice




Without Vsync,



eh: Ah, OK. Had the 2x multiplier (what was it, prescale?) enabled. But still 20-25% with one slice against 5-15% without Vsync.

2x = internal texture is twice the size = 4x more pixels for GPU to render.

winuae.7z should reduce new low latency vsync CPU usage slightly, also adds support for D3D9 + Windows XP combination (not tested).