WinUAE 3.4.0 beta series

[Toni Wilen]

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

Beta 3:

- PCI ES1370 fixed.
- (Missed from b1 log): CPU Idle logic has been completely changed, now it only has two states, inactive and active. Active state changes internal CPU speed state to approximate and active equals fastest possible mode. Old logic was never good enough. CPU usage was never low enough and it didn't prevent audio glitches.
- Another b1 missed log entry: conditional register breakpoints, break when any CPU register matches (equals, smaller, larger, range). More information in debugger help.
- Do not use new CPU Idle mode in PPC-only configs.
- Low latency vsync really fixed. Can also fix other CPU usage related problems in other modes.
- Hardware info panel up/down button disable logic improved.
- Bitplane DMA overrun 1 cycle adjustment, now it matches real A1200 100%. Possible Disk/Audio/Sprite DMA slot conflicts are not yet emulated. (Causes graphics glitches on real hardware)
- uaegfx vblank interrupt hang fixed.
- Network OSD led was invisible.

[thomas]

UAEGFX 8bit has completely wrong colors. Was right in 3.3.0.

[Toni Wilen]

Originally Posted by thomas

UAEGFX 8bit has completely wrong colors. Was right in 3.3.0.

256 color WB works fine. Also I tried few RTG demos that use 256 color. They also worked fine.

Sorry but I am not going to run any annoying PC ported games that require megabytes of memory and usually crash when even tiny requirement is slightly wrong.

[amilo3438]

Just to confirm that the problem from the post #19 has been fixed with this version.
(post #19 -> http://eab.abime.net/showpost.php?p=...5&postcount=19 )

ps.
On my usual A500 game config. the title screen of Jim Power on the 3.4.0 beta shows CPU usage over 120%, while on the 3.3.0 only sometimes goes (jump) over 100%. (not sure what is the reason). Maybe its time for a new PC.

[thomas]

Originally Posted by Toni Wilen

256 color WB works fine.

No, it doesn't. See screenshots of wallpaper above. Plain Workbench 3.1 with Picasso96, UAEGFX:640x480x8bit CLUT.

Seems like normal colors initially set by Palette prefs are correct, but colors set later by WBPattern are not.

[Toni Wilen]

Originally Posted by thomas

No, it doesn't. See screenshots of wallpaper above. Plain Workbench 3.1 with Picasso96, UAEGFX:640x480x8bit CLUT.

Seems like normal colors initially set by Palette prefs are correct, but colors set later by WBPattern are not.

Right, confirmed. I thought those test demos did change the palette on the fly but apparently they did not..

[vagrant]

With beta 3, I'm still getting screen-tear effect in the top portion of display - it only happens with low latency & no buffer mode.. there is no tearing with double/triple buffering enabled.
I can't remedy it by increasing sound buffer either.
Also getting intermittent audio pops & dropouts in low latency modes (with and without buffering).

[Toni Wilen]

Originally Posted by ED-209

With beta 3, I'm still getting screen-tear effect in the top portion of display - it only happens with low latency & no buffer mode.. there is no tearing with double/triple buffering enabled.
I can't remedy it by increasing sound buffer either.
Also getting intermittent audio pops & dropouts in low latency modes (with and without buffering).

Nothing done yet to fix this specific problem. Previous fixes only fixed other related bugs. I assume this is WASAPI pull mode side-effect and DirectSound still works normally?

[AMIGASYSTEM]

Ciao Toni, You can affect I did a test with Doom II with two different porting Adoom and DoomAttack to a 800x600 8-bit resolution (miniaturized)

[vagrant]

Originally Posted by Toni Wilen

Nothing done yet to fix this specific problem. Previous fixes only fixed other related bugs. I assume this is WASAPI pull mode side-effect and DirectSound still works normally?

Hmm, well DirectSound in low latency no buffer mode works, but it needs a significant amount of buffer to be error free (4+).. any less and cpu usage & fps spike badly, causing the same negative effects as wasapi pull mode (without the screen tearing).

[Toni Wilen]

Originally Posted by ED-209

Hmm, well DirectSound in low latency no buffer mode works, but it needs a significant amount of buffer to be error free (4+).. any less and cpu usage & fps spike badly, causing the same negative effects as wasapi pull mode (without the screen tearing).

My point was that if directsound works the same as in 3.3.0, it confirms there is no more other recently introduced problems to fix before it is time for wasapi pull mode tuning for vsync modes.

[vagrant]

Yep it is the same as 3.3.0 - same size buffer needed for stability.

[psykicko]

Originally Posted by psykicko

If i disable my work partition then it loads os4 fine.

I got the same result with beta2. No change there. Also with winuae.7z

I tried beta 3 and same there. Also when accessing Amiga Early Startup boot options i see all partitions except my work partition.

[Toni Wilen]

Originally Posted by psykicko

I tried beta 3 and same there. Also when accessing Amiga Early Startup boot options i see all partitions except my work partition.

Does it appear if you move it to SCSI ID 0? (SCSI ID 1 is not differently configured in CSPPC menu?)

[AMIGASYSTEM]

OK Toni, With last winuae.7z (29-8 ‏‎20:06) Adoom e Duke Nukem 3D now is good

[psykicko]

Originally Posted by Toni Wilen

Does it appear if you move it to SCSI ID 0? (SCSI ID 1 is not differently configured in CSPPC menu?)

If i move it to SCSI ID 0 then also my system (DHO) is gone from the boot menu. About CSPPC menu, i dont know how to access it. I havent changed anything in it. I googled and said you have to press esc while boot, some says holding both mouse buttons and esc but that only shows the normal boot menu.

[Toni Wilen]

Originally Posted by psykicko

If i move it to SCSI ID 0 then also my system (DHO) is gone from the boot menu. About CSPPC menu, i dont know how to access it. I havent changed anything in it. I googled and said you have to press esc while boot, some says holding both mouse buttons and esc but that only shows the normal boot menu.

Exact same config works with 3.3.0?

I don't see any other solutions than to adjust your config until something interesting happens. (remove unneeded drives, change controller to UAE). There is nothing in the logs that would explain it.

(Boot menu can be entered with ESC key but you probably need to tick "one second reboot pause" in misc panel or you'll need to be extremely fast..)

[psykicko]

Originally Posted by Toni Wilen

Exact same config works with 3.3.0?

I don't see any other solutions than to adjust your config until something interesting happens. (remove unneeded drives, change controller to UAE). There is nothing in the logs that would explain it.

(Boot menu can be entered with ESC key but you probably need to tick "one second reboot pause" in misc panel or you'll need to be extremely fast..)

This time i was really fast and got the menu. Everything here in scsi is set to auto. I havent changed anything. Some more info that you maybe dont see in the screenshot.

In the cd & harddrives menu both dh0 and dh1 says Volume HDF but the files are named like system.hdf and work.vhd. Dont think it helps but anyway more info. Check on screenshot the filesize. I use only the 2 selected files as images. dh2 is just a shared windows drawer.

I will do as you say, try disabling and changing stuff. But yes with 3.3.0 everything worked. The problem came from the first beta of 3.4.0 and forward.

EDIT: I changed to UAE instead of csppc for work partition and now it works. I changed the system to UAE too. However sometimes when i use reset in the gui the system wont boot. it just flashes pink like it fails somewhere and resets... and resets... forever. But a restart makes it boot ok again or if i restart winuae itself. But then im happy it boots again

[michaljarz]

Since 3.4.0.b02 JIT always switched to the "Indirect" mode. Is it normal? "Direct" mode requires special settings?
(EDIT: Previously I wrote about Wazp3D. In Win XP doesn't work, but in Win 10 works... and in Win7 also works...)

[Toni Wilen]

Originally Posted by michaljarz

Since 3.4.0.b02 JIT always switched to the "Indirect" mode. Is it normal? "Direct" mode requires special settings?
(EDIT: Previously I wrote about Wazp3D. In Win XP doesn't work, but in Win 10 works... and in Win7 also works...)

It is not normal and it is already fixed. Including lots of edge cases if "weird" or "too much" RAM is enabled where wrong mode was selected causing possible crashes.

Originally Posted by psykicko

EDIT: I changed to UAE instead of csppc for work partition and now it works.

Ok, it could be scsi emulation related (nothing done there but side-effects are possible). Put hdf back in CSPPC scsi, run winuae with -log -scsiemulog command line parameters with only one drive mounted (in CSPPC SCSI unit that since 3.4 fails to detect anything), wait until KS boot screen appears (and no drive detected), quit, attach winuaelog.txt.