AmigaOS 4.1FE RTG screen gets trashed

[FlynnTheAvatar]

Hi,

Everytime I switch my AmigaOS 4.1 FE installation to non-RTG screen mode, the screen is almost black after switching back. This even happens if I just test one of the Low-Res/High-Res (AGA) modes. Please see the attached image.

Most icons and the window bar will stay black even after closing/reopening the windows. The only way to restore the display is to select another RTG screen mode or reboot.

Please find the configuration and Winuae logs attached.

I could not find any configuration where this issues does not happpen. I tried WinUAE 3.5 and 3.6, uaeglx and Picasso IV, disabled all UAE extension (UAE rom). With uaeglx the screen does not turn black, but is overwritten with garbage (repeated window bars, ...).

Has anybody any idea what is causing this issue?

Thank you and best regards,
-Flynn

[Toni Wilen]

How exactly does it happen? Simply changing screen mode using screenmode prefs to native and then back?

[FlynnTheAvatar]

Yes, testing a native screen mode in Screenmode prefs is enough. Complete switching to a native mode does not trigger this problem because switching back fixes the issue.

Initially, I noticed it when I tried to open a default screen in C. Same issue there.

[FlynnTheAvatar]

Small video for reproducing this issue.

[ Show youtube player ]

Please note that this was recorded in FS-UAE 2.9.7dev2. I can reproduce the issue the same way in WinUAE 3.5.0 and 3.6.0.

[Toni Wilen]

I can duplicate it (but only by pressing test in screenmode prefs). Unfortunately I can't see anything in emulation that would affect it, especially when PicassoIV and uaegfx are totally different.

OS4 seems to clear the VRAM when switching to native but does not restore all required data when switching back.

[FlynnTheAvatar]

Thank you for testing. So, you think this an OS4 bug and not an emulation problem?

Not sure if this helps, but I can trigger the issue when opening a highres screen:

/*
 *Compile like this:
 *gcc open_screen.c -o open_screen -lauto
 * 
 */
#include <proto/intuition.h>
#include <proto/dos.h>

int main() {
	struct NewScreen ns = {
    0, 0, 640, 256, 4, /* left, top, width, height, depth */
    0, 1,              /* DetailPen, BlockPen */
    HIRES,             /* ViewModes */
    CUSTOMSCREEN,      /* Type */
    NULL,              /* Font */
    "Test",            /* DefaultTitle */
    NULL,              /* Gadgets */
    NULL,              /* CustomBitMap */
  };

	struct Screen* myScreen = IIntuition->OpenScreen(&ns);

	IDOS->Delay(500);

	IIntuition->CloseScreen(myScreen);


	return 0;
}

[FlynnTheAvatar]

Mmh, it does not happen when I open a hires interlaced screen.

[Toni Wilen]

Originally Posted by FlynnTheAvatar

Thank you for testing. So, you think this an OS4 bug and not an emulation problem?

I don't know but there is chance it is not emulation only problem. No one probably uses native modes in OS4..

[AMIGASYSTEM]

To me on OS4.1 the screen does not turn black when I change screenmode up High-Res, see video attached

[FlynnTheAvatar]

Sorry, I cannot open your video. So, I cannot check, but I think you use uaegfx, don't you?
Yes, with uaegfx the screen does not turn black. Try dragging the workbench screen down after switching the screen mode. This trashes the screen for me. It does not turn black, but the complete screen is overwritten with garbage - repeating parts of windows bars and stuff.

I will try to upload a screenshot later.

[AMIGASYSTEM]

Strange that you can not see a video file, i uploaded the video on youtube now I think you can see it. To me the black screen does not happen either with Picasso or with UaeGfx, Both OS4.1 Classic and OS4.1 FE , in the attached video OS4.1 use a Picasso Screen.


[ Show youtube player ]

[FlynnTheAvatar]

Thank you for uploading the video to Youtube.


Yes, switching to a high res native screen mode and back with either "Use" or "Save" works fine.


Please just try to "Test" the native screen mode. In this case the RTG screen is not closed and a new temporary native screen is created. After returning from the test (closing the native test screen) my RTG screen turns black.


Or you could run any app that opens a native screen (e.g. CygnusED). The important step is that the RTG screen is not closed.

[AMIGASYSTEM]

Originally Posted by FlynnTheAvatar

Or you could run any app that opens a native screen (e.g. CygnusED). The important step is that the RTG screen is not closed.

CygnusED is set to Native Screen, opens on a native screen

Can you attach your config (.uae) so the text on my system?

[FlynnTheAvatar]

My config is included in the zip in the first post.

But no, you opened CygnusED on the public screen. Please try following steps:
1) Set your screen mode to any Picasso IV mode (e.g. "Board 0: 1024x768 BGR 24")
2) Start CygnusED
3) Click on "Set screen size and type"
4) Select "PAL highres"
5) Switch to Workbench screen by clicking on the small icon on the top right of the screen bar (or press left Amiga + N)

[AMIGASYSTEM]

With UAE-GFX no problem, with Picasso IV I receive a black screen


[ Show youtube player ]

[FlynnTheAvatar]

Okay, I re-tested with UAE-GFX and could not reproduce the issue anymore. Picasso IV still gives me a black screen, but UAE-GFX with 16bit color is fine.

Sorry about the wrong initial error description.

[AC/DC HACKER!]

This seems to fit for something I've noticed. I do not notice this with Picasso 4 driver. Only UAEGFX. Either 68K driver or Picasso96 Picasso 4 driver renamed for UAEGFX PPC being used for OS 4.x.. The screen(s) don't have to be dragged down or up.

Look at image filenames for descriptions.

Edit: Looks like I have to check into this further than 16MB...

Edit 2: Looks like VRAM of 32MB is the number and after that it's doing well at.

Edit 3: Several hours later, I came back to test some more. I shifted UAEGFX VRAM to 512MB and clicked Start. As OS 4.x was loading, the background stuff was loading and the background image hadn't loaded yet...everything stopped except the default OS 4.x sound. Mouse was locked, F12 worked so I clicked reset.
It's also crashing with A2065 enabled and X-Surf 100 Z3 disabled...using Odyssey browser. Hmm...

I'm going to do several runs with A2065 only now and Picasso 4. Yup, it does the same crash with A2065 and graphic glitches don't appear. I'll do more later..