WinUAE 2.8.0 beta series (Was 2.7.1)

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2710b13.zip

Beta 13:

- Canceling video or audio codec selection dialog will disable audio or video recording. This has been broken for long time, it was impossible to record video only or audio only (except in wav mode).
- 64-bit build now also supports wintab tablet API.
- Fixed some slirp Windows specific 64-bit compilation issues.
- Fixed JIT + more compatible enabled emulated Amiga crash. (b9)
- If "always on top" option is enabled, GUI is also opened with "always on top" flag.
- gfx_linemode=none (no doubling) was loaded as doubled mode.
- Check and limit 2x software filter height value if size is larger than allocated buffer size, preventing display buffer overflow crash.
- Debugger now disassembles most FPU instructions correctly but some of them may look strange..
- Disassembler MULL and DIVL fully decoded.
- Support "INPUTDIMS" D3D shader variable. Used by some shaders.
- JIT FPU rare bug workaround, FPU constant optimization introduced in 1200b3 disabled. (Code looks correct, it works correctly except in some very rare situations, real cause may be some unknown JIT side-effect)

[acd2001]

Action Replay function is ok in b7
but bugged in b8-b13

[vagrant]

B13 working nicely here, thanks toni

edit:
Changing CE & JIT settings on the fly with whdload still appears unstable compared to beta 9 & previous.
It can crash on startup or exit.. usually 'H1' cpu state.
Problem is that it's intermittent and doesn't happen too often.. so is hard to reproduce!

edit2:
Found a way to always reproduce
Nexus 7 demo, whdload.
When demo is quit, always results in 'H1' cpu state. It does not happen in beta 9.
Demo launch disables JIT and enables CE. Demo cleanup enables JIT and disables CE.

[Toni Wilen]

Originally Posted by ED-209

Changing CE & JIT settings on the fly with whdload still appears unstable compared to beta 9 & previous.

Does http://www.winuae.net/files/b/winuae.zip fix it?

Originally Posted by acd2001

Action Replay function is ok in b7
but bugged in b8-b13

More information needed, works for me. (Which Action Replay version? How is it not working? What config?)

[acd2001]

More information needed, works for me. (Which Action Replay version? How is it not working? What config?)

Windows XP Sp3 512Mb (Old computer, i know....)
Action Replay Mk III v3.17 (1991)(Datel Electronics).rom
crc32 009F7768

Amiga emulation boot correcty but AR don't activate at pag key pressing

[Toni Wilen]

Originally Posted by acd2001

Windows XP Sp3 512Mb (Old computer, i know....)
Action Replay Mk III v3.17 (1991)(Datel Electronics).rom
crc32 009F7768

Amiga emulation boot correcty but AR don't activate at pag key pressing

Much better, thanks. Fixed and above url updated.

[vagrant]

Originally Posted by Toni Wilen

Does http://www.winuae.net/files/b/winuae.zip fix it?

It's worse unfortunately, now launching nexus 7 instantly results in H1 state.

I've found another way to always reproduce problem.
When I run 'museum' demo, it appears to run and quit ok. Then when I try to run any other demo it crash with H1 state. Again, no problem with b9.
Log attached from b13.

[Toni Wilen]

What about now? At least I couldn't duplicate random crash anymore.

[vagrant]

Ok tried the updated file and nexus 7 still crashed at launch with unrecoverable H1 + output window.

It looks like the problem is still related to 'more compatible' + JIT.
I've found that if I simply load my config to workbench, open gui, disable JIT, close gui = H1 crash + output window.
I'll attach screen & log of this exact event.

If I first disable 'more compatible' I get no problems at all.

[Toni Wilen]

Originally Posted by ED-209

Ok tried the updated file and nexus 7 still crashed at launch with unrecoverable H1 + output window.

It looks like the problem is still related to 'more compatible' + JIT.
I've found that if I simply load my config to workbench, open gui, disable JIT, close gui = H1 crash + output window.
I'll attach screen & log of this exact event.

If I first disable 'more compatible' I get no problems at all.

I still can't duplicate it. Please "minimize" your config (no fullscreen, no vsync, disable all unneeded expansions, uaescsi, bsdsocket etc..) first, make sure it still crashes, and attach the config file.

Does it happen with 020 and 040 CPUs too?

Does it still happen if you boot from WB disk? (with harddisks removed)

[vagrant]

Ok.. I'm still using the updated winuae.zip.

If I boot my normal 030 config with RTG disabled it is completely stable. I can run nexus 7 and everything else no problem - no crashes.

Now, with RTG enabled again, it of course still crashes when JIT is disabled and 'more compatible' ticked.
If I choose 040 it's crashes the same.
If I choose 020 - no crash! Completely stable..

I'll attach my normal config.

[Toni Wilen]

Thanks. Really should be fixed now.

[Supamax]

Originally Posted by Toni Wilen

Thanks. Really should be fixed now.

I'm always so damn amazed by the speed with which Toni solves issues!

[Mclane]

Originally Posted by Supamax

I'm always so damn amazed by the speed with which Toni solves issues!

That crystal ball is damn useful

[vagrant]

Originally Posted by Toni Wilen

Thanks. Really should be fixed now.

No thank you sir, running smoothly again

[Gundam]

Originally Posted by Supamax

I'm always so damn amazed by the speed with which Toni solves issues!

Only Toni makes it possible!

[thomas]

This new resolution detection/switching or not switching is terrible!

Please allow a combination of options so that PAL:Hires 640x256, PAL:Hires Interlaced 640x512 and Super72:Superhires Interlaced 800x600 are all displayed with correct aspect ratio without manual intervention! Actually all screen modes from Storage/Monitors should be displayed with correct aspect automatically.

And please don't disable vertical line mode options when horizonzal resolution autoswitch is enabled. At least not until it works correctly. Currently vertical line mode is always switched to "single" when autoswitch is enabled.

And what shall these "10% 33% 66%" options mean? I don't see any difference.

Actually the autoswitch option is of no use and never was. But at least up to now the modes mentioned above worked with autoswitch disabled. This has been destroyed now, too.

[Toni Wilen]

What are you talking about? (Quite difficult to understand when all required information is missing, config, when it stopped working the usual! Seeing plain "It does not work" "report" from regular poster is quite disappointing..)

Autoswitch has never had anything to do with correct aspect ratio.

EDIT: Also describe what are you trying to do because above explanation does not really make any sense for me.

[thomas]

Originally Posted by Toni Wilen

What are you talking about? (Quite difficult to understand when all required information is missing, config, when it stopped working the usual! Seeing plain "It does not work" "report" from regular poster is quite disappointing..)

Autoswitch has never had anything to do with correct aspect ratio.

EDIT: Also describe what are you trying to do because above explanation does not really make any sense for me.

Seems like Beta 11 is the culprit.

A4000 quickstart, no filter, no scaling, no aspect correction, 800 x 600 fullscreen, centered in both directions, hires (normal), doubled

Boot the attached ADF and try the different saved screen modes. The screenshots show how they should look like.

In 2.7.0 - beta 10 all modes work correctly except 800 x 150 which is only half-height.

With autoswitch enabled only the interlaced modes work correctly, but all of them. Non-interlaced modes are forced to single line mode.

In beta 11 - 13 only PAL and NTSC modes work correctly when resolution is set to hires. Super72 modes work correctly with superhires.

Autoswitch only works if resolution was set to superhires before it is enabled.
Non-interlaced modes are still forced to single line mode.

[Toni Wilen]

Originally Posted by thomas

Non-interlaced modes are forced to single line mode.

But that is exactly how it was designed to do. Display horizontal and vertical mode is set to be as small as possible without losing pixels. Made for game/demo purposes where most screens are lores/non-laced but title/loading/etc screens may be in hires for best performance and quality. (Doubling using filter panel is faster than software based doubling)

Non-interlaced: single (nothing is lost in single mode)
Interlaced: double (need both lines or every other pixel line would be lost)

Same for horizontal: if lores, use lores mode, if hires (even if there is single mostly invisible line of hires), select hires mode.

I think you expected it to do something different?

EDIT: I can't see any difference between latest beta and 2.6.1 with autoswitch enabled. (Except Super72 which was "fixed")

EDIT2: Of course I always use windowed mode, I never test using fullscreen until it is 110% confirmed it is required.