Drastic difference in game with WinUAE 5

[Seiya]

I notice differences about WinUAE 5.0.0 and WinUAE 4.10.1 about the game Tapper.

WinUAE 5.0.0 (kick 1.3, OCS, 1 MB Chip RAM)


WinUAE 4.10.1 (kick 1.3, OCS, 1MB Chip RAM)

[Aladin]

Tapper (WHDLG) works well with winuae 5 ... (I didn't change anything in my settings when I updated winuae)

perhaps a configuration problem to be modified in your settings ...

[Seiya]

maybe for the graphics could be a solution, but for audio uses default WinUAE settings.
could you try the floppy version so at least i can see if i have to change scripts

[Seiya]

I tried other games and It is not a WinUAE issues as i thought, because i tested with 4.2.1, 4.9.1 and 4.10.1 with the same scripts and it works. With 5.0.0 doesn't works because maybe some changes are not compatibie with some configurations script and so impossibile to write from scratch.

[Aladin]

I just tested with the ADF version and my KS1.3 configuration (68000 Full-ECS and 1 MB Chip with 1 MB Fast) and everything works fine.

[Seiya]

with WinUAE 4.10.1, but also 4.2.1 and 4.9.1 it works with:
Kickstart 1.3, OCS, 1 MB Chip RAM and none bogomen and none fastmem.

WinUAE 5.0.0 not works in that config and trying "your" config it works.

[gimbal]

You shouldn't edit the OP to be completely different, that is actually against the site rules if I recall correctly. Just add a foot note or something.

[Mclane]

Tried Tapper (demo) under the recently released 5 and apart from it needing an a500+ to work, it was fine, no such issues, smooth as silk, sound fine and no garbage.

On an a500, I got a HALT2 after it read track 71

[Seiya]

Originally Posted by gimbal

You shouldn't edit the OP to be completely different, that is actually against the site rules if I recall correctly. Just add a foot note or something.

i put now the reason to have changed first post.

Originally Posted by Mclane

On an a500, I got a HALT2 after it read track 71

making an A500 config not works and you have HALT2. I resolved with putting 1 MB Chip RAM with old WinUAE version.
WinUAE 5.0.0 emulation is more precise than before.

WinUAE 5.0.0:
kick 1.3, OCS, 1MB chip, it not work
kick 1.3, ECS, 1MB Chip, 1 MB fast, it works

WinUAE 4.10.1, 4.2.1, 4.9.1
Kick 1.3, OCS, 1MB Chip, it works

[TCD]

Originally Posted by gimbal

You shouldn't edit the OP to be completely different, that is actually against the site rules if I recall correctly. Just add a foot note or something.

https://eab.abime.net/faq.php?faq=ea...ads_vandalized

Not sure that it's meant for this situation (especially in a support subforum).

[Seiya]

well, you can recover original post, but without video link because i removed from youtube.
Than i will post 2 picture of those i notice about WinUAE 4.10.1 and 5.0.0

or close this one and i make a new topic

edit:
i rewrite the original post (more or less) to better understand this topic and to understand the reply.

[Seiya]

now i understand: it's not a memory problem. It is chipset issue.

This game with WinUAE 5.0.0 run with only 1MB Chip RAM, but with ECS chipset.
Old versions of WinUAE run with 1MB Chip RAM and OCS Chipset.

I tried both in Gamebase both WinUAE standalone from autostart.
with OCS chipset have many graphics glitches and bad sound.
with ECS chipset is all ok

With many other games there is no problems, but this game show a strange effect simply changing from OCS to ECS

[Toni Wilen]

This is not a bug and a bug at the same time.

OCS >512k Chip RAM was supposed (If I remember correctly) by default to work like ECS Agnus (DMA can address more than 512k) because these kind of "illegal" configs do exists and they would break.

But something happened and now it works like real A500 + OCS + 1M Chip RAM: CPU sees 1M Chip RAM but Agnus DMA can only see first 512k, high address bit that selects between lower or upper 512k is missing, lower 512k is always selected. (This config exists in real world and at first it might appear to work because programs usually don't need more than 512k of chip ram and as long as all data that needs to be Agnus DMA accessible gets located in first 512k of Chip RAM. Trouble only starts if DMA accessible data ends in upper 512k..) Advanced chipset Agnus size settings also don't do anything when OCS Agnus.

In next version I'll keep this default behavior but make it possible to use Advanced chipset 1M/2M Agnus size to override it if OCS Agnus.

[Seiya]

thanks Toni

[ztronzo]

If you find the floppy version of a game called "Crack" you can also test that.. I recall it needed OCS chipset instead of ECS to play correctly

[Toni Wilen]

Originally Posted by ztronzo

If you find the floppy version of a game called "Crack" you can also test that.. I recall it needed OCS chipset instead of ECS to play correctly

This thread has nothing to do with those OCS/ECS differences.

Topic is >512k chip RAM with OCS Agnus which is impossible in real world and currently UAE works like real OCS hardware with "1M chip RAM". It wasn't supposed to do that by default.

[madaxe]

Hi folks;

I have the same problem. When I run WinUAE 4.10.1 with OCS, 1.3 ROM, 1 MB Chip RAM, I get this:



But I when run WinUAE 5.0.0 with the same configuration of above, I get this and eventually the system crashes:



If I change to ECS Agnus or keep OCS and simply add 512 KB Slow RAM the game works perfectly.

Thank you for explaining why this happens, Tony

Cheers,
José Mário aka MadAxe

[Toni Wilen]

5.1 betas should already fix this.

Technically it is correct behavior (what real HW does) but it is not what older versions did and also 5.0 wasn't supposed to do that by default.

[21stcentury]

It works well with A500+ and A600 configurations in MagicUAE / WinUAE 5.0.
It doesn't running in A500 / A500 1mo meaning the game needs ECS.

[madaxe]

Originally Posted by Toni Wilen

5.1 betas should already fix this.

Technically it is correct behavior (what real HW does) but it is not what older versions did and also 5.0 wasn't supposed to do that by default.

I suggest that an option should be added to WinUAE to "solve" this issue.
Well, if OCS with 1 MB Chip RAM doesn't exist in real hardware WinUAE should be accurate. But WinUAE is an emulator and sometimes emulators have features that don't exist on real machines.
In my case isn't a great problem because I have only one saved configuration with OCS and 1MB Chip RAM and I don't mind to change it to ECS Agnus.