Gfx glitch in menus

[Octopus66]

Hi all - does anyone know what might be causing this corruption on the Delete gfx symbol in OS3.2? Or know where a good place to start looking would be?

[AMIGASYSTEM]

If I remember correctly this problem has already been discussed, is yours a standard 3.2 system, or but mixed other Amiga OS?

[Octopus66]

Clean 3.2 install

[AMIGASYSTEM]

Give it a try, try to copy the gadgets !

[Swe_Kryten2x4b]

I got that with the aminet-version of P96 (in other words, an older version). It disappeared when I upgraded to the paid version.

[AMIGASYSTEM]

Octopus66 said he has a "Clean 3.2 install", then from the screenshot it seems to be a PAL screen, so no RTG installation !

I however don't use the paid Picasso drivers and I have no problem, see screenshot

[Swe_Kryten2x4b]

Originally Posted by AMIGASYSTEM

Octopus66 said he has a "Clean 3.2 install", then from the screenshot it seems to be a PAL screen, so no RTG installation !

I however don't use the paid Picasso drivers and I have no problem, see screenshot

Now that you mention it, it does look loke a a PAL screen.

It seems more things can trigger that behavour in that case.

The attached file is what I get with the paid version of P96. With the unpaid version I get what the OP got.

[Octopus66]

Actually this is my fault for not being clear. I should have said "standard" OS 3.2 install, as I do have P96 installed for use with ShapeShifter.

Does anyone know why this happens when I am not using an RTG screen? Any resolution other than paying for the newer version of P96?

[Thomas Richter]

Originally Posted by Octopus66

Does anyone know why this happens when I am not using an RTG screen?

BltMaskBitMapRastPort() is buggy on interleaved bitmaps in your old version.

[Matt_H]

Originally Posted by Thomas Richter

BltMaskBitMapRastPort() is buggy on interleaved bitmaps in your old version.

So simply having an older P96 installed - even when not using an RTG screen - can trigger this bug?

[AMIGASYSTEM]

Originally Posted by Octopus66

Actually this is my fault for not being clear. I should have said "standard" OS 3.2 install, as I do have P96 installed for use with ShapeShifter.

That's why I was asking you if you had a standard clean system

Originally Posted by Matt_H

So simply having an older P96 installed - even when not using an RTG screen - can trigger this bug?

Yes the old versions create this problem, there are versions like Picasso96-2_1.e that if you save a PAL OS3.2 screen it doesn't start anymore, grey screen and graphic artifacts (lines of various colors).
Also Picasso96-v2.0 has some problems, better instead the Picasso96 1.25 and 2 2.1b versions, even if the gfx symbol problem is present also in these versions.

[Octopus66]

Originally Posted by Matt_H

So simply having an older P96 installed - even when not using an RTG screen - can trigger this bug?

My current workaround is not loading the monitor drivers unless needed i.e. moving to Storage folder. Quite strange though.

[Thomas Richter]

Originally Posted by Matt_H

So simply having an older P96 installed - even when not using an RTG screen - can trigger this bug?

Like I said, this is a known and fixed defect in BltMaskBitMapRastPort(). SetPatch fixes it on affected systems, but P96 is loaded after SetPatch, so that doesn't help.