Since 2.4.0 including 2.4.1b7 little display corruption

Hello,

I have seen little problem since 2.4.0 and in all beta 2.4.1 including the latest b7. It can be seen in "The Settlers disk 1 of 3" (the intro) as soon as it starts. There are lots of flashing parts during the vertical scrolling, then later the dog is split between shifted contour and content.

In 2.3.3 and Hardware/CPU and FPU tab had a "Fastest possible, but maintain chipset timing" now replaced by "Fastest possible". The 2.3.3 version did not exibit this problem while any version >=2.4.0 exhibit it as soon as the "Fastest possible" option is set.

To reproduce: Start WinUAE and select "A1200" in the quickstart tab, then put the compatibility slider to the middle and check "Fastest possible" in CPU and FPU tab then boot "The Settlers disk 1 of 3".

Thank you again for this fantastic software, it was very useful to prepare a new HD for my A1200+Microbotic 030+882@50 and it brings a so powerful Amiga

Ridrok

[Toni Wilen]

It is probably normal, fastest possible has faster CPU emulation, possible much faster when custom chipset is also being used (vs RTG mode), compared to older version.

Games usually don't like "too fast" CPU. Immediate blitter may help.

Thank you for your answer.

Immediate blitter helps yes, but not in the initial vertical scrolling.
I did not see other display bug apart this one, but I don't use WinUAE a lot.

Is there an equivalent of the former "Fastest but maintain timings" to start from a HD image which requires a descent speed for applications but that is compatible with games on HD?

Regards,
Ridrok

[Toni Wilen]

Originally Posted by Ridrok

he former "Fastest but maintain timings" to start from a HD image which requires a descent speed for applications but that is compatible with games on HD?

It is same setting, only difference is that CPU is faster. Chipset timing is still the same. Fastest possible means CPU emulation is as fast as possible, it can and will change between versions.

Actually 2.3.3 and older had very badly designed fastest possible mode without JIT. (Speed difference can be 2x-4x!) JIT speed is the same.

Note that you would have gotten same problem if your PC's CPU would have been (much) faster, even with 2.3.3

CPU speed adjustment may also help.