WinUAE 4.0.0 beta series

[Viceroy]

Originally Posted by Toni Wilen

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

The DH1 drive is a folder on my separate Amiga HD which is a 500GB drive
The DH1 drive won't open on the latest beta, but works fine on last stable version, screenshot of C:info enclosed, cheers

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

If I try to boot up with the DH1 in configs machine won't boot up, I have to add it after startup, then reset again all fine on stable version

Stable version C:info

https://drive.google.com/open?id=1Ic...IyaAtBSC-OFbDq

[Toni Wilen]

It starts to look this has to be caused by something else. Attach your config file and winuaelog.txt, thanks.

[Viceroy]

Originally Posted by Toni Wilen

It starts to look this has to be caused by something else. Attach your config file and winuaelog.txt, thanks.

There you go Toni, thanks for looking into this ;-)

https://drive.google.com/open?id=1jt...uGclZ_hYxqnhKf

[Retro-Nerd]

winuae.7z should reduce new low latency vsync CPU usage slightly

Indeed. Works especially better with emulated AGA machines and 4 slices than before, maybe 10-15% lower usage.

[Viceroy]

Originally Posted by Toni Wilen

It starts to look this has to be caused by something else. Attach your config file and winuaelog.txt, thanks.

I have sent you a PM Toni with a link for the Harddrives

[r.cade]

I'm sure this was mentioned in the thread and I just missed it. I had terrible tearing with the new LL modes, but it turned out it was related to my filter settings. I always used "Automatic Scaling" and that doesn't work right in the new modes. I set back to "Default" and it was fine.

[Toni Wilen]

Originally Posted by Viceroy

There you go Toni, thanks for looking into this ;-)

https://drive.google.com/open?id=1jt...uGclZ_hYxqnhKf

Wrong logs are included, tick logging checkbox in misc panel to enable winuaelog.txt generation.

Originally Posted by Retro-Nerd

Indeed. Works especially better with emulated AGA machines and 4 slices than before, maybe 10-15% lower usage.

Hopefully this don't break anything, it is difficult to balance between stability and cpu usage..

Originally Posted by r.cade

I'm sure this was mentioned in the thread and I just missed it. I had terrible tearing with the new LL modes, but it turned out it was related to my filter settings. I always used "Automatic Scaling" and that doesn't work right in the new modes. I set back to "Default" and it was fine.

There is still no autoadjustment that fits slice positions correctly if Amiga overscan size screen is not near-1:1 mapped vertically to host monitor. Especially bad when game has large blank bar at the bottom which autoscale removes.

[Viceroy]

Here are correct logs I think Toni, I also PM'd you a link if you wanted to test the drives yourself, thanks again.

https://drive.google.com/open?id=16V...SRJJaASh70_Csw

[Toni Wilen]

Originally Posted by Viceroy

Here are correct logs I think Toni, I also PM'd you a link if you wanted to test the drives yourself, thanks again.

Thanks. winuae.7z should fix it. (HD unit number confusion between HDFs and directory harddrives)

[Viceroy]

Originally Posted by Toni Wilen

Thanks. winuae.7z should fix it. (HD unit number confusion between HDFs and directory harddrives)

Sorry Toni a bit confused, (winuae.7z should fix it) whats this please?

[DamienD]

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

[Viceroy]

Originally Posted by DamienD

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

This works perfect thanks Toni & DamionD :-)
How did you find this DamionD?

[DamienD]

Originally Posted by Viceroy

This works perfect thanks Toni & DamionD :-)
How did you find this DamionD?

The URL is Toni's temporary WinUAE version between betas when he targets specific issues.

[Viceroy]

Ah right ;-)

[Leandro Jardim]

Originally Posted by Toni Wilen

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!

The color bars are flickering all over the screen but mainly at the top. They seem to compete for its place, sometimes. The first beta it was 99% stable all the time.

[Toni Wilen]

Originally Posted by Leandro Jardim

The color bars are flickering all over the screen but mainly at the top. They seem to compete for its place, sometimes. The first beta it was 99% stable all the time.

Does -busywait command line parameter "fix" it? (100% CPU use is normal in this test mode)

[Leandro Jardim]

Originally Posted by Toni Wilen

Does -busywait command line parameter "fix" it? (100% CPU use is normal in this test mode)

No, they seem more unstable. While there is some tearing at the top of the screen on both "modes", the debug color bars are much more unstable.

[mark_k]

Has anyone noticed keyboard issues, with keys sometimes repeating several times quickly? On Windows 10 1709, I can't see the issue with 3.6.1 but can with 4.0.0b1 and b2.

My usual config has JIT, fastest possible, with CPU idle slider all the way to the right. Windowed, no vsync. It happens sometimes with that. It seems to happen much more often if I move the CPU Idle slider a few notches to the left.

The problem doesn't happen all the time, and seems to require typing quickly to trigger. For example, opening a CLI and typing qpqpqpq (etc.) quickly might result in this text:
qpppqpqpqpqpqpqqqpqpqpppqqqqppppq

With CPU Idle slider a few notches to the left the repeating seems quicker, so typing 010101 (etc.) might give
0111000000011100001111100000001111

[bernd roesch]

i have same problem. the timer run too fast can see in amiga clock too, when cpu idle is much right. on older winuae there is no such timer problem. sync in winuae gui is on

[Toni Wilen]

I was just debugging it (I noticed it also very rarely). Possibly fixed now.