WinUAE 3.4.0 beta series

[Toni Wilen]

Originally Posted by Retro-Nerd

I have problems with the low latency vsync in fullscreen to. Shows only a black screen. After pressing the F12 key i get an image but can't control the mouse though. Other sync modes seems fine.

I'll delay this fix for later because there is some annoying incompatibility with nvidia gsync display (even when gsync is switched off. I upgraded to Acer X34 few months ago) and low latency vsync. It works very badly. I need to find out how to make it work again. Perhaps secondary normal monitor works normally or something..

[Retro-Nerd]

Ah, ok. If you have a test version sometime later i will try it of course.

[mark_k]

I tested a config with Fastlane, 68040 and 32MB Z3 RAM on 3.4.0b1. I get a dialog saying "Out of memory or too much Z3 autoconfig space configured." when I load it and click Start. No dialog in 3.3.0.

Log output for 3.3.0 and 3.4.0b1 plus config attached. (I'm testing in Wine btw.)


Autoconfig board list:
Card 01: '<no name>' no autoconfig.
Card 02: 'Z3 Fast RAM'
a9.0a.f0.00.21.40.00.00.00.00.00.00.00.00.00.00
MID 8512 (2140) PID 10 (0a) SER 00000000
Z3 0x40000000 0x10000000 32M RAM 0
Card 03: 'Fastlane'
91.0b.70.00.21.40.00.00.00.00.08.00.00.00.00.00
MID 8512 (2140) PID 11 (0b) SER 00000000
Z3 0x42000000 0x12000000 32M ROM 1
END
NATMEM: Not enough memory for Z3REAL!
Out of memory or too much Z3 autoconfig space configured.

[Toni Wilen]

Originally Posted by Arnie

Logs & config attached.

Config works in 3.3 but not with the WinUAE.7z from post #28

Fixed. Mainboard hardwired autoconfig devices (A3000/CDTV DMAC) were movable but they need to be first device.

Ticking custom board order and making sure CDTV DMAC is first in the list should also fix it.

[Toni Wilen]

Originally Posted by mark_k

I tested a config with Fastlane, 68040 and 32MB Z3 RAM on 3.4.0b1. I get a dialog saying "Out of memory or too much Z3 autoconfig space configured." when I load it and click Start. No dialog in 3.3.0.

Log output for 3.3.0 and 3.4.0b1 plus config attached. (I'm testing in Wine btw.)


Autoconfig board list:
Card 01: '<no name>' no autoconfig.
Card 02: 'Z3 Fast RAM'
a9.0a.f0.00.21.40.00.00.00.00.00.00.00.00.00.00
MID 8512 (2140) PID 10 (0a) SER 00000000
Z3 0x40000000 0x10000000 32M RAM 0
Card 03: 'Fastlane'
91.0b.70.00.21.40.00.00.00.00.08.00.00.00.00.00
MID 8512 (2140) PID 11 (0b) SER 00000000
Z3 0x42000000 0x12000000 32M ROM 1
END
NATMEM: Not enough memory for Z3REAL!
Out of memory or too much Z3 autoconfig space configured.

This should be already fixed in winuae.7z

[Toni Wilen]

Originally Posted by mark_k

Does WASAPI audio always use pull mode in beta 1?

Yes.

Could you write about how you achieved that sometime?

There was some errors in previous attempts to reduce latency which actually could have increased it by 1 field in some situations and now when Amiga program reads mouse/joystick input for the first time during field, host input queue is handled first, before returning input state to emulated Amiga.

[Toni Wilen]

Originally Posted by psykicko

With 3.4.0 beta my system never loads to workbench. Its only black and in the status says "halt3". With previous 3.3.0 everyhing loaded fine. Attached is my config file. Say if you need anything more from me.

If above winuae.7z still does not work, attach also log.

[Arnie]

Originally Posted by Toni Wilen

Fixed. Mainboard hardwired autoconfig devices (A3000/CDTV DMAC) were movable but they need to be first device.

Ticking custom board order and making sure CDTV DMAC is first in the list should also fix it.

Problem with that is that I can't get CDTV DMAC to be first in the list and booting it as in the pic results in a grey screen.

EDIT: Scratch that. I re-downloaded the Winuae fix and it's working now .

[Toni Wilen]

Originally Posted by Locutus

Mouse cursor is missing in on Cirrus Logic RTG screen in the new beta.

Also fixed. (winuae.7z)

Next official beta in 1-2 days, then it is time to debug other issues.

[psykicko]

Originally Posted by Toni Wilen

If above winuae.7z still does not work, attach also log.

it doesnt work with the http://www.winuae.net/files/b/winuae.7z either

[Toni Wilen]

Originally Posted by psykicko

it doesnt work with the http://www.winuae.net/files/b/winuae.7z either

I can't duplicate. Difference must be either in CSPPC flash rom menu settings or your boot media.

Does switching off JIT make any difference? Removal of all harddrives except boot drive?

[michaljarz]

My config also crash at load (XPSP3, WB3.1). Attached logs with 3.3.0 (works ok) and latest winuae.7z (crash). I noticed it's load when deleted "uaegfx" and "uaegfx.card" from devs:monitors.
(sorry for my english)

[Arnie]

OS4.1 PicassoIV

PicassoIV is not loading with my config in 3.4. Works in 3.3.

Config +Logs attached.

EDIT: Moving the PicassoIV up the hardware list results in a crash. Logs attached.

[AMIGASYSTEM]

Thanks Toni, I discovered with surprise that now with OS4.1 can a Switch UAE Zorro III / Picasso IV without changing prefs screen mode on Workbench (conversely crashes). On OS3 (AFA OS) is not so, i have to hand-edit the prefs in ScreenMode, Attaching video exhaustive, set Youtube HQ.

[ Show youtube player ]

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Thanks Toni, I discovered with surprise that now with OS4.1 can a Switch UAEGfx / Picasso IV without changing prefs screen mode on Workbench (conversely crashes). On OS3 (AFA OS) is not so, i have to hand-edit the prefs in ScreenMode, Attaching video exhaustive, set Youtube HQ.

Yes but what does this has to do with WinUAE betas? OS4.x just has improved Picasso96. OS3.x Picasso board handling is just painful.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Yes but what does this has to do with WinUAE betas? OS4.x just has improved Picasso96.

Excuse me Toni, on WinUAE 3.3.0 you could not do the Switch

[Toni Wilen]

Originally Posted by AMIGASYSTEM

Excuse me Toni, on WinUAE 3.3.0 you could not do the Switch

Worked for me. (EDIT: if you have 32-bit Windows, it can easily cause issues depending on RTG board size, location etc.. 3.4.0 handles it better.)

[Toni Wilen]

Originally Posted by amilo3438

Config: Quickstart, A500 (most common)

I'd wait a bit before everything stabilizes before benchmarking too much..

Ps. Nice to see it still working on WinXPSP3 !
Not sure is the problem related to XP ! (can someone confirm the same)

XP is still supported. (XP support in Visual Studio also isn't going away in next version either)

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Worked for me. (EDIT: if you have 32-bit Windows, it can easily cause issues depending on RTG board size, location etc.. 3.4.0 handles it better.)

In fact I have Win7 32 Bit

[Toni Wilen]

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

Beta 2:

- Needed natmem space also included IO only Z3 boards but only RAM and VRAM boards should count. Fixes most "out of memory" errors.
- RTG VRAM outside of natmem space handling is back, RTG works again in 32-bit Windows in "Real" Z3 mode. (also in "UAE" mode if RTG was not first Z3 board and previous board(s) was large enough)
- A2065 didn't work if accessed by PPC CPU.
- Mainboard built-in autoconfig devices were movable (CDTV and A3000 DMAC).
- Hardware info panel move up/down buttons are now disabled when unmovable item is selected.
- Automatic Z3 mapping mode selected UAE mode even when it was not needed. (no JIT direct and not enough natmem space)
- Natmem allocation is still used (if possible) even when starting emulation without direct jit to have better chance for on the fly direct jit switching.
- Low latency vsync fixed.

This should fix most b1 bugs but may also introduce new ones, internal memory handling is still rewritten (some odd memory handling stuff since the JIT was first added are finally going away)