WinUAE 4.4.0 beta series

[Toni Wilen]

Does both 32-bit and 64-bit version cause the game crash identically? Did both 32-bit and 64-bit 4.3.0 work? It is possible it simply accidentally worked in 4.3.0 due to whatever random timing side-effect etc..

[DamienD]

Originally Posted by Toni Wilen

Does both 32-bit and 64-bit version cause the game crash identically? Did both 32-bit and 64-bit 4.3.0 work? It is possible it simply accidentally worked in 4.3.0 due to whatever random timing side-effect etc..

Don't worry... and I never use the 64-bit version.

We know the issue is probably JIT related; the problem for me is that if I turn off JIT, the game runs ok'ish but is quite jerky.

I've spent the last 40 minutes or so playing around with various JIT options; none have worked and the game still crashed at least 5 out of 10 times

...but finally I believe I've found the perfect configuration; I've tested this 30 times in a row and not one crash!!!

So, here's what I changed from the last 68030 CPU / JIT config:

• Unticked "More compatible".
• Changed the "Cache size" from my usual 16MB set with any JIT games --> 2MB.

No idea why this works; maybe it makes sense to you?

Anyway, I've extremely happy now!!!

Edit: just tested another 20 times, it crashed once.

1 crash out of 50 are very good statistics in my book; compared with previous.

[Toni Wilen]

The point was that if 64-bit works differently or identically is very important detail. (4.3 and different 4.4 betas)

[DamienD]

I mean, I can test the 64-bit version if you want me too; but I'm in the office today so this won't be until later tonight.

[Toni Wilen]

Another test case: does it happen if using directory filesystem? (It would enable easier debugging, for example if program loads some audio file or something on the fly that causes the problem)

[DamienD]

Originally Posted by Toni Wilen

The point was that if 64-bit works differently or identically is very important detail. (4.3 and different 4.4 betas)

Home now and have tested with http://www.winuae.net/files/b/winuae64_4400b6.7z using the old configuration i.e. 68030 (More compatible unticked) / Fastest possible / JIT / FPU 68882 / 16MB Cache size.

This was worse than the 32-bit version; crashed 8 out of 10 tries.

The 32-bit version with the same above old configuration crashed 5 out of 10 tries.

Do you want me to test with the 64-bit version of v4.3.0? With the 32-bit version of v4.3.0 it never crashed at all.

[Toni Wilen]

Yes. And also using only directory harddrive (and/or all game data in ram disk but it probably needs a bit too much RAM..).

[DamienD]

Using the old configuration i.e. 68030 (More compatible unticked) / Fastest possible / JIT / FPU 68882 / 16MB Cache size...

In the 64-bit version of v4.3.0 it behaved exactly like the 32-bit version of v4.3.0 i.e. 0 crashes out of 10 tries.

Originally Posted by Toni Wilen

And also using only directory harddrive (and/or all game data in ram disk but it probably needs a bit too much RAM..).

Ok, and test this via http://www.winuae.net/files/b/winuae_4400b6.7z I assume?

[DamienD]

Originally Posted by Toni Wilen

And also using only directory harddrive (and/or all game data in ram disk but it probably needs a bit too much RAM..).

Originally Posted by DamienD

Ok, and test this via http://www.winuae.net/files/b/winuae_4400b6.7z I assume?

So have now copied all .HDF contents to a Windows folder from inside emulation.

Changed the old configuration i.e. "68030 (More compatible unticked) / Fastest possible / JIT / FPU 68882 / 16MB Cache size" to point to this Windows folder and tested...

It only crashed 1 out of 10 times with b6

I'm really confused; I thought it was better to use a .HDF as opposed to a Windows folder?

[DamienD]

Hi Toni,

I've been testing all the usual games I do with any new beta / stable release.

Seems that Payback and Simon The Sorcerer II: The Lion, The Wizard And The Wardrobe are now quite slow indeed when compare to 4.3.0.

I'm having to adjust my configs to accommodate, but even afterwards, they are not running as well as in 4.3.0.

Both games use a 68030 CPU. Does this mean I should really be testing any games in my collection that have this CPU set?

[Toni Wilen]

Originally Posted by DamienD

Hi Toni,

I've been testing all the usual games I do with any new beta / stable release.

Seems that Payback and Simon The Sorcerer II: The Lion, The Wizard And The Wardrobe are now quite slow indeed when compare to 4.3.0.

I'm having to adjust my configs to accommodate, but even afterwards, they are not running as well as in 4.3.0.

Both games use a 68030 CPU. Does this mean I should really be testing any games in my collection that have this CPU set?

Don't adjust anything until the real problem is found..

Attach one of the configs (before any adjustments).

Originally Posted by DamienD

So have now copied all .HDF contents to a Windows folder from inside emulation.

Changed the old configuration i.e. "68030 (More compatible unticked) / Fastest possible / JIT / FPU 68882 / 16MB Cache size" to point to this Windows folder and tested...

It only crashed 1 out of 10 times with b6

I'm really confused; I thought it was better to use a .HDF as opposed to a Windows folder?

Either isn't really "better". It depends as usual...

Run with "-filesyslog2" (and with -log) and check if some file access related log line appears just before the crash.

[DamienD]

Originally Posted by Toni Wilen

Don't adjust anything until the real problem is found..

Attach one of the configs (before any adjustments).

In The Zone! you will find "Payback & Simon II_configs.zip"

Originally Posted by Toni Wilen

Either isn't really "better". It depends as usual...

Run with "-filesyslog2" (and with -log) and check if some file access related log line appears just before the crash.

Ok, I will test with the old config using http://www.winuae.net/files/b/winuae_4400b6.7z, those command line options and the .HDF.

[DamienD]

Originally Posted by Toni Wilen

Either isn't really "better". It depends as usual...

Run with "-filesyslog2" (and with -log) and check if some file access related log line appears just before the crash.

Originally Posted by DamienD

Ok, I will test with the old config using http://www.winuae.net/files/b/winuae_4400b6.7z, those command line options and the .HDF.

This makes absolutely no sense what-so-ever...

If I run "WinUAE -filesyslog2 -log", the game didn't crash once in five attempts using the old config i.e. "68030 (More compatible unticked) / Fastest possible / JIT / FPU 68882 / 16MB Cache size".

Removed "-filesyslog2 -log", tested again and crashed first time.

[Toni Wilen]

Originally Posted by DamienD

In The Zone! you will find "Payback & Simon II_configs.zip"

Does Simon have (about) same speed if you change CPU panel CPU Frequency to 8x?

Originally Posted by DamienD

This makes absolutely no sense what-so-ever...

If I run "WinUAE -filesyslog2 -log", the game didn't crash once in five attempts using the old config i.e. "68030 (More compatible unticked) / Fastest possible / JIT / FPU 68882 / 16MB Cache size".

Removed "-filesyslog2 -log", tested again and crashed first time.

It adds logs of logging which will slow down emulation. This probably means game does have some very timing sensitive bug..

[DamienD]

Originally Posted by Toni Wilen

Does Simon have (about) same speed if you change CPU panel CPU Frequency to 8x?

Don't worry about Simon II.

I played it for more than 5 minutes in v4.3.0; and my config was too slow.

I've now changed this to "Fastest possible" and untick "More compatible".

This is fine in b6 also.

Originally Posted by Toni Wilen

It adds logs of logging which will slow down emulation. This probably means game does have some very timing sensitive bug..

Yeah.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_4400b7.7z
http://www.winuae.net/files/b/winuae64_4400b7.7z

Beta 7: (max 2-3 weeks before final)

- Fixed Misc panel statefile text box working strangely when typing. Also default statefile path and .uss extension is added if missing.
- CPU multiplier in prefetch mode (support added in b1) wasn't saved to config file.
- CPU multiplier is set to pre-4.4 defaults when loading old config files.
- CPU multiplier (if prefetch/ce) is changed to default multiplier when CPU model is changed.
- "Default" filter mode now enables aspect ratio correction and scales to window/screen size. Disabled previously active GUI elements that are not compatible with current filter mode.

[Viceroy]

Thank you ;-)

[ross]

Originally Posted by Toni Wilen

- "Default" filter mode now enables aspect ratio correction and scales to window/screen size. Disabled previously active GUI elements that are not compatible with current filter mode.

When I launch in Quickstart mode now the view appear squashed (with black bars at top and bottom).
If I select 'no scaling 1x/1x' all back to normal (like the default on previous versions).

EDIT: more info.
Host 1920x1080 in 16:9, default 720x568 windows, PAL mode

[Toni Wilen]

Right, forgot about that side-effect when using default window size.. Should be easy fix..

[Toni Wilen]

Background: "default" scaling mode should be something that is mostly ok for most normal users. Which means Amiga view should be scaled to selected fullscreen/window size (even if it means scaling artifacts) and aspect ratio correction should be enabled.

winuae.7z now in "default" scaling mode sets aspect ratio correction off if window/screen is close enough to 4:3. Only if it isn't close enough, aspect ratio correction gets enabled (=black bars may appear).

I hope this is good enough. All other scaling modes are (and should be) fully configurable. Only "default" is special.