WinUAE 3.3.0 beta series

[Toni Wilen]

Originally Posted by Locutus

Please disregard my request, it must have been due to not having all Dx runtimes installed (and its always a mystery exactly which one you need from winetricks...).

d3dx9_43.dll is the dll that is required and comes only with DX9 redistributable.

But shouldn't wine have built-in version of most DLLs?

[Retroplay]

I run latest WinUAE with no additional dll files just fine in Wine (PlayOnLinux) in Mint KDE 17.3 x64.

[Locutus]

Originally Posted by Toni Wilen

d3dx9_43.dll is the dll that is required and comes only with DX9 redistributable.

But shouldn't wine have built-in version of most DLLs?

i think that if you use the WINE Builtin WinUAE fails to detect it or something similiar (i havent reverified that case).

Wine does supply its own D3D implementations etc but in reality to actually get any modern games to run you need to install the real DX runtimes :-)

[Tomislav]

Which Wine version you have? WinUAE on my Wine 1.8 don't have problem with finding D3D.

[Toni Wilen]

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

Beta 9:

- Fixed swapped audio channels if stereo separation was set (b1 cleanup missed code path)
- Fixed uaehf.device SCSI emulation sense data possible crash/wrong status. (trap update related)
- 32M UAE RTG board was always address space aligned. It is wrong in UAE mapping mode.
- Only swallow hardware horizontal and vertical mouse movement when in mouse driver mode, not mouse wheel.
- Improved programmed refresh rate hsync start and end validation to prevent crashes if weird mode is set. (BoggleDop / Sanity)
- Added hardfile virtual bad block support. uaehf.device and hardware SCSI emulation only. Create geometry text file (<name of hardfile.hdf>.geo) in same directory as hardfile, add badblocks=<blocks> line. (<blocks> can be range, 10-100 or single value or multiple ranges/values, for example 10-100,200,1000-20000) Max 8 bad block values/ranges supported. Error is returned if block in badblock range is attempted to be read or written.
- OS4.x UAE trap mode now uses hybrid busy wait mode. Performance has improved again, directory filesystem speed is now fully usable and uaegfx is also noticeably faster.
- UAE indirect trap stability updates.

[Aegis]

Originally Posted by Toni Wilen

Beta 9:
- OS4.x UAE trap mode now uses hybrid busy wait mode. Performance has improved again, directory filesystem speed is now fully usable and uaegfx is also noticeably faster.

Setting aside the fact that you don't like Quake as a benchmark (for QEmu's slow soft-float performance)

Beta 8 x64: 320x200 28 fps
Beta 9 x64: 320x200 36 fps

Very nice!

[Toni Wilen]

Originally Posted by Aegis

Setting aside the fact that you don't like Quake as a benchmark (for QEmu's slow soft-float performance)

Beta 8 x64: 320x200 28 fps
Beta 9 x64: 320x200 36 fps

Very nice!

It is better (but not much) than usual Quake benchmark. At least PPC emulation is exact same in this comparison.

[Leandro Jardim]

HALT3 with AmigaOS 3.9, Genesis and uaenet.device. I have put a symlink to Genesis on WBStartup drawer, and is on boot that WinUAE halts. The WinUAE version is 3.3.0 b9.

[Toni Wilen]

Originally Posted by Leandro Jardim

HALT3 with AmigaOS 3.9, Genesis and uaenet.device. I have put a symlink to Genesis on WBStartup drawer, and is on boot that WinUAE halts. The WinUAE version is 3.3.0 b9.

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

[Leandro Jardim]

Originally Posted by Toni Wilen

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

Thanks it is fixed. There is another issue, this time Genesis can't connect with A2065 emulation on AmigaOS 3.9. The issue happened first time before of this fix.

[Toni Wilen]

Originally Posted by Leandro Jardim

Thanks it is fixed. There is another issue, this time Genesis can't connect with A2065 emulation on AmigaOS 3.9. The issue happened first time before of this fix.

No config or netlog command line parameter: you really sure you selected slirp mode A2065? ("works for me")

[Leandro Jardim]

Originally Posted by Toni Wilen

No config or netlog command line parameter: you really sure you selected slirp mode A2065? ("works for me")

Ok, now I have put the config in the zip file and ran WinUAE with -netlog parameter too. Sorry. I think I must have done something wrong at that time, I think that probably a2065 was set to "cable disconnected" mode, but the issue persists. I receive this message from Genesis: "iface_getaddr: SIOCGIFADDR: Device not configured". The Genesis config is the same as I used for uaenet, I only changed the SANA driver from "uaenet.device" to "DEVS:Networks/ethernet.device".

[Toni Wilen]

Originally Posted by Leandro Jardim

Ok, now I have put the config in the zip file and ran WinUAE with -netlog parameter too. Sorry. I think I must have done something wrong at that time, I think that probably a2065 was set to "cable disconnected" mode, but the issue persists. I receive this message from Genesis: "iface_getaddr: SIOCGIFADDR: Device not configured". The Genesis config is the same as I used for uaenet, I only changed the SANA driver from "uaenet.device" to "DEVS:Networks/ethernet.device".

I think it is better to do this properly: when it did last work? Just wondering because there is no a2065 changes in 3.3.0 betas..

EDIT: add also -a2065log2 command line parameter.

[Leandro Jardim]

Originally Posted by Toni Wilen

I think it is better to do this properly: when it did last work? Just wondering because there is no a2065 changes in 3.3.0 betas..

EDIT: add also -a2065log2 command line parameter.

That is not needed anymore, sorry. I was accessing the Internet with uaenet.device but when I changed the device driver to ethernet.device (my a2065 device driver), it denied to work. Now it is working again but I needed to run GenesisWizard from scratch. I was suspecting this before, but I was not believing which that was really necessary. For some reason its not sufficient changing the device driver directly with GenesisPrefs. Sorry.

[Photon]

Waiting with baited breath for 3.3.0 Can I use latest beta and silence the beta software warning somehow? Edit: didn't help. Trying to run this (tried with default A1200 config, same+8MB Z2, 030+FPU+Z3...) cos I sold both my 8MB fastram and MX1230. Maybe it's the ROM (doubtful)? Don't have 3.0 as file to test. Same in older stable versions.

[Toni Wilen]

Originally Posted by Photon

Waiting with baited breath for 3.3.0 Can I use latest beta and silence the beta software warning somehow? Edit: didn't help. Trying to run this (tried with default A1200 config, same+8MB Z2, 030+FPU+Z3...) cos I sold both my 8MB fastram and MX1230. Maybe it's the ROM (doubtful)? Don't have 3.0 as file to test. Same in older stable versions.

You didn't even tell what goes wrong. But I think the answer is: run setpatch first.

[Toni Wilen]

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

Beta 10:

- if uaenet.device is online and packet(s) have arrived but there is no pending CMD_READ/CMD_READORPHANs: wait about 2s before dropping it, it is possible that multiple packets will arrive so quickly that Amiga-side TCP/IP stack don't have time to queue more read commands before packets get dropped.
- uaenet.device stability fix.
- Loading config with unplugged joystick or mouse inserted in either port: previous device was not autoselected.
- Filter panel scaling mode active and mouse driver enabled: mouse got stuck in a corner in some situations.
- Screenshot input event set to toggle-mode in Input panel: key/button press = create screenshots continuously every frame, following key/button press = stop automatic screenshots.
- one genlinetoscr function (16-bit 4x horizontal stretch) used genlock function in non-genlock mode.
- Adaptive Sync "vsync" mode added. Optimal setting designed for G-Sync/FreeSync monitors. Also allows 100/120Hz black frame insertion mode. Not very stable yet. (Don't try to use without adaptive sync hardware..)
- 68040 MMU mode SR M-bit handling was missing. 68060 SR M-bit handling was not correct.
- Disable bsdsocket.library if indirect UAE Boot ROM is enabled, it is not (yet?) compatible.

[Photon]

Originally Posted by Toni Wilen

I think the answer is: run setpatch first.

Yep, my startup-sequence needs a tweak (too lazy to invoke boot without s-s and run SetPatch manually all the time). It handles all my real Amigas but these specs land somewhere in between. I do run it without > NIL: so I should have paid attention

[arti]

GL applications (QuarkTex) are not working in WinUAE 3.3.0 b10 (not tested on previous betas)
They work in 3.2.2.

[Toni Wilen]

Originally Posted by arti

GL applications (QuarkTex) are not working in WinUAE 3.3.0 b10 (not tested on previous betas)
They work in 3.2.2.

Last working beta? Without JIT? Using 32-bit build? (Was QuarkTex even supposed to work with 64-bit?)