WinUAE 4.9.2+ beta series

[enigma776]

Originally Posted by Toni Wilen

64-bit version has wrong CPU requirement (requires AVX). Will be fixed in next beta.

Yeah that will do it lol

[rutra80]

In case it was lost as the last post of 4th page:

Originally Posted by rutra80

Scanlines settings on Filter tab don't work as expected with Integer scaling - 1:1 makes no scanlines at all, only changes brightness, 1:2 looks like 1:1 should etc.
Toni could you please by the way make separate settings for laced & non-laced modes? Separate shaders would be awesome too...

[Toni Wilen]

Originally Posted by rutra80

In case it was lost as the last post of 4th page:

Isn't that happened in 4.9.1 too? If yes, I'll move this to other thread beta specific bugs are usually much more important and others easily get lost)

[rutra80]

In 4.9.1 they seem wrong only after enabling - after switching to other pattern they begin to look properly.
In beta they're wrong all the time.

[reenstix]

Originally Posted by Toni Wilen

I don't know.. Try reducing Z3 RAM to 64M and VRAM to 64M too. 32-bit Windows versions can have relatively small per-process address space limits which can cause unexpected problems if too much RAM is allocated.

I can reproduce this problem on Windows 7 32bit and Windows 10 32bit as well. Even with Z3 RAM set to 32MB and VRAM set to 8MB. On 64bit version of Windows 7 and Windows 10 this problem doesn't exist.

[MagikGimp]

Is there a problem with emulated CD-ROM drives with the betas?
Unfortunately I can only use b2 due to my also ancient hardware but I see no mention of this anywhere in the changelogs.

Initially CDs were working correctly but after switching to other Configs I noticed that I could not mount CD disk images any more. Thinking that I was using a setup with hardware that didn't support CD-ROM drives (I tried IDE and SCSI both to no avail) I switched back to the first config (AmiKit v8.5.2) only to find no CD mounting there now either. However, on downgrading back to WinUAE v4.9.1 lo and behold it reappears.

Am I doing something wrong? Have things changed in 9.2 or is this indeed suspicious of something problem somewhere?

[Toni Wilen]

Originally Posted by rutra80

In 4.9.1 they seem wrong only after enabling - after switching to other pattern they begin to look properly.
In beta they're wrong all the time.

Right, it has been broken at least since 4.9.0 or even more.

Originally Posted by reenstix

I can reproduce this problem on Windows 7 32bit and Windows 10 32bit as well. Even with Z3 RAM set to 32MB and VRAM set to 8MB. On 64bit version of Windows 7 and Windows 10 this problem doesn't exist.

Quite strange that 32bit/64bit makes a difference.
Check following to make sure there are no "wrong" settings:
- Display panel shows 32 bit mode (even if using windowed mode)
- RTG panel "Match host and RTG color depth if possible" option is not ticked. (or better, tick off all options)
- Make sure in Amiga side Screenmode prefs shows exact same mode name. (BGR vs RGB etc..)

[Ponki1986]

Originally Posted by reenstix

I can reproduce this problem on Windows 7 32bit and Windows 10 32bit as well. Even with Z3 RAM set to 32MB and VRAM set to 8MB. On 64bit version of Windows 7 and Windows 10 this problem doesn't exist.

I asked my friends and they confirmed that the problem is only in the 32 bit version.

[Toni Wilen]

Originally Posted by Ponki1986

I asked my friends and they confirmed that the problem is only in the 32 bit version.

Did above changes fix it? If not, which Amiga side mode is in use? Check if changing it fixes it. (You also have all 16-bit modes enabled which is not common config). EDIT: and switch off JIT when testing.

btw, your previous logs don't have any Picasso96 PIP logging. Are you really sure it is PIP window and not some kind of "emulated" PIP?

btw2, "fallback native open: 'Z:\WinUAE\winuae_dll\CopyMemAIO.alib' = 126, 126". Remove this at least temporarily.

Originally Posted by MagikGimp

Is there a problem with emulated CD-ROM drives with the betas?

Shouldn't be any and works fine here. How did you mount it? (there are multiple different ways) Attach config + winuaelog.txt from both previously working version and from latest beta.

[Ponki1986]

1. Workbench has been using UAEGFX 32Bit BGRA mode since forever. But I've also tried others with no results.

2. I have all 15/16 Bit modes turned on, because for example the game Earth2140 needed the PC mode, or the GnGEO emulator needs 15 Bit modes because it displays wrong colors.

3. Emulated PiP? When I turn on XP compatibility, all programs like PiPView, CyberPiPView, BlurScopePiP plugin for AmigaAMP, PiPpinEVD plugin for ShapeShifter, GeneticSpecies game - RTG Master library, movie players like MooVid, RiVA, all display the content correctly in the WB window. Without XP Mode, all of the above-mentioned programs also run fine, but their windows are black.

4. I wrote about the problem with this function a long time ago, after you released version 4.2. The AMIGASYSTEM user even sent me a picture of his 3.1 system, where the situation was identical. Then I did not use CopyMemAIO yet.

5. My friends wrote to me that they checked their configuration and the problem appears only in the 32Bit version, both Windows 7 and 10. Also the user REENSTIX wrote:

I can reproduce this problem on Windows 7 32bit and Windows 10 32bit as well. Even with Z3 RAM set to 32MB and VRAM set to 8MB. On 64bit version of Windows 7 and Windows 10 this problem doesn't exist.

6. I checked all possible options available in the WinUAE settings.

In the screenshots below I started ClassicWB. The configuration I set up is MC68030 + 68882 without JIT. AGA, UAEGFX 32 VRAM. Chip 2 MB, Fast 32 MB. Without any extra settings. I didn't install anything extra, no patches. As you can see, the problem is still the same.

https://drive.google.com/drive/folde...Im_38Dueghim3a

[Toni Wilen]

Ok, it is real PIP window (I guess you didn't run any PIP programs when you created your previous logs? You can delete this attachment.)

Could you recreate logs: use same config, use working "mode", boot to WB, run any PIP program. Quit. Then do exact same with non-working "mode". (I need to find some other way to debug this if logs are practically identical...)

[Ponki1986]

The files are again available at this link:

https://drive.google.com/drive/mobil...Im_38Dueghim3a

I have saved the logs from version 4.9.1, and 4.9.2 B3. Just a strange thing, because Beta 3 does not respond to running it in XP mode. You can use Direct3D 11, but the PiP windows are blank, or black. Changing Direct3D to 9 does not improve the situation. Version 4.9.1 behaves like 4.9.2 Beta 1 and 2, i.e. after running in XP mode you can only use Direct3D 9, but then PiP works too.

Anyway, I started WinUAE, loaded the configuration and started AmigaOS. I then displayed the same image using CyberPiPView and PiPView. Later I ran GeneticSpecies twice at 640x480 and 320x256 resolution. Both in a PiP window.

[Toni Wilen]

Should be fixed now (https://www.winuae.net/files/b/winuae.7z), please confirm.

This was quite stupid bug. Overlay limit checks had one comparison that compared Amiga side VRAM end against host side bitmap end which accidentally passed if 64-bit Windows (64-bit Windows allocates memory from higher addresses) but always incorrectly detected write outside of bounds if 32-bit.

I had to install 32-bit Windows 7 in VM to be able to find the bug. No wonder it made no sense at all

[Ponki1986]

Everything works great !!! Huge respect and thanks.

[Toni Wilen]

https://download.abime.net/winuae/fi...nuae_4990b4.7z
https://download.abime.net/winuae/fi...ae64_4990b4.7z

Beta 4: (Version number bumped to 4.9.9 because 68000 IPL emulation update is done)

- Remaining IPL fixes (LINK, UNLK, MOVE to SR/CCR, AND/EOR/OR SR/CCR, CPU wait state IPL fix).
- Emulated Paula side-effect that affects IPL timing. IPLx line state changes from low to high (IPL is active low) are about 0.5 CCK later than high to low transitions. This delays CPU IPL change detection by 2 CPU clocks if any IPL line had low to high transition. CPU accepts IPL change only if has been stable for 2 CPU clocks. (for example 3 to 5 has delay, 4 to 5 does not)
- Enable only WASAPI audio by default.
- Debugger break point command accepts number of hits before breaking to debugger (f Nxx <address> where xx is number of hits required)
- uaegfx overlay limit checks compared Amiga side VRAM end against physical host side bitmap end which accidentally passed if 64-bit Windows. Overlay window was usually empty if 32-bit Windows. (It might have worked in some configurations when using Z2 uaegfx)
- GUI Help button is now always available and opens if exists: (in priority order) winuae.chm, winuae.pdf. If neither is found, help web page is opened (without asking first like previously)
- It is still possible to run windowed WinUAE if desktop is 16-bit but it can cause graphics problems. Not sure if this needs to be supported anymore.

68000 based A500 like unexpanded (Fast RAM expansion is supported) configurations should be now 100% cycle-accurate. (If there are no bugs, many edge cases need complex and very carefully timed cycle accurate tests that are not easy to do)

Note that this does not mean all features are fully emulated, for example OCS and ECS Denise mid-screen resolution changes are not pixel accurate. Accurate as in if resolution change is not carefully coded, there can be few extra or missing pixels when resolution changes. AGA does not have this side-effect.

[Ponki1986]

Thanks a lot. Now WinUAE offers me everything I could wish for:

- FloppyBridge support via the UAE-Configuration command
- Image display with Direct3D 11
- A working PiP/Overlay function
- A performance increase of around 30 MiPS, I now have up to 520
- All the other great features and capabilities

Thanks again.

[rutra80]

RTG Integer Scaling is not integer on my system (W10, RTX3060, 2560x1440).

Also, although I have 120Hz set on RTG tab, only 60Hz modes are available, but after reset on Amiga side I do get the 120Hz modes.

[BjornHeimdall]

Thanks for this great emulator.

1. Display: Scanlines + Filter 1.5x - Not displayed correctly.


2. Why not emulator window centering on screen when starting up. I have different configurations with different window resolutions, all windows opening up others starting pixel?

[Toni Wilen]

Originally Posted by rutra80

RTG Integer Scaling is not integer on my system (W10, RTX3060, 2560x1440).

Also, although I have 120Hz set on RTG tab, only 60Hz modes are available, but after reset on Amiga side I do get the 120Hz modes.

This is practically useless information, only possible reply is to buy a better system

Screen capture that shows the problem, config and winuaelog.txt from both last working and latest beta is needed.

[Toni Wilen]

Originally Posted by BjornHeimdall

Thanks for this great emulator.

1. Display: Scanlines + Filter 1.5x - Not displayed correctly.

I don't think these are new in 4.9.2 betas? Display panel scanlines have never worked very well if filter scaling is enabled (and can't work because they are drawn before filtering). Use Filter panel scanlines.

2. Why not emulator window centering on screen when starting up. I have different configurations with different window resolutions, all windows opening up others starting pixel?

What do you mean? Do you mean window position relative to desktop? Window initial position is global setting which can be annoying if different configs have very different window sizes.