Crash in Fullscreen when pressing F12

[Vairn]

I have had this issue in Winuae for a while now, (like years)

If I am running Winuae in Fullscreen non-RTG if I press f12, it will crash.

Is this a known issue, or am I doing something stupid (Highly probable )

I've added a dmp file, and a copy of the log.
Not 100% if the dmp is related to the crash, because it hasn't changed the last 3 times I ran and ,made uae crash.

[Toni Wilen]

Looks like DirectDraw (which can have issues, it isn't really supported anymore) + some filter is in use but config is set to D3D9: fix probably is as simple as installing DX9 redistributable or switching to D3D11 mode.

[DamienD]

@Vairn; just in case you need the URL for the DX9 redistributable: https://www.microsoft.com/en-us/down...s.aspx?id=8109

[Vairn]

Ok, so reinstalling the DX9 runtime didn't help, still crashed. (it was set to the dx9 renderer in the misc section.)

If I change this to DX11 it doesn't crash, woo.

@DamianD, so I have written a python script to convert all your configs for me
woo.

[DamienD]

Originally Posted by Vairn

@DamianD, so I have written a python script to convert all your configs for me
woo.

That's a bit of over kill Vairn

...all you needed to do was use NotePad++ to replace this line "gfx_api=direct3d" with this line "gfx_api=direct3d11" in all configuration files:

[Vairn]

I'm a programmer, overkill is second nature.

Sent from my Pixel 2 XL using Tapatalk

[Foebane]

DamienD, will that change in the config mean "no more DX9 runtime libraries needed"? And will everything else running look and sound identical?

[Toni Wilen]

Yes. Direct3D11 is supported since Windows 7 SP 1 (requires single non-mandatory update from Windows Update because supporting old method is annoying) and is fully included since Windows 8.

Full Direct3D9 was never included with any Windows version. DX9 redistributable is always required.

[DamienD]

Personally I cannnot use Direct3D11 on my laptop due to the image being fully stretched...

I have set scaling off in my configuration files / on my video card and it works perfectly with Direct3D9 though.

[Toni Wilen]

You are doing it wrong

You should use native aspect ratio modes + filter panel automatic aspect ratio ticked. If you use non-native aspect ratio and/or resolution, there are two scaling steps: first winuae to selected output resolution and then output to actual display native resolution and this second scaling step is done either GPU or monitor and user control options are limited or non-existing. You don't want two scaling steps.

Most compatible option (automatically works with any aspect or resolution) is to select "native" as resolution, filter panel automatic aspect ratio enabled and filter mode like TV (max) or integer scaling.

[DamienD]

Ok, not the first time that I tried following yours / Retro-Nerd's advise with this.

I always end up with something like the attached no matter what settings I try / adjust under "Filter" (1st and 2nd attached images); or totally stretched over the whole laptop screen.

Anyway, to be honest, I'm very happy how I have things set up with Direct3D9 (3rd and 4th attached images, but for some reason, the black borders on the left / right don't capture in the screenshots). They are the correct aspect though

[Foebane]

I wouldn't worry, DamienD, DirectX 11 doesn't solve all problems, and indeed, some of the oldest games I have on Steam still demand those runtime libraries, they actually install themselves when I install the game on it, in fact.

But I WILL change my configurations to DirectX 11, Hardware mode.

[DamienD]

Originally Posted by Foebane

I wouldn't worry, DamienD

I'm not worried at all; plus the 1000+ people who have my collection / configs seem to be happy also

...but I will always try new methods if it improves things and of course I listen to Toni's advise.

Unfortunately for me though, for whatever reason, Direct3D11 doesn't seem to play ball.

My laptop is 8 years old though so...

I guess at the end of the day, do whatever works for you on your setup

[Toni Wilen]

Originally Posted by DamienD

Ok, not the first time that I tried following yours / Retro-Nerd's advise with this.

I always end up with something like the attached no matter what settings I try / adjust under "Filter" (1st and 2nd attached images); or totally stretched over the whole laptop screen.

Anyway, to be honest, I'm very happy how I have things set up with Direct3D9 (3rd and 4th attached images, but for some reason, the black borders on the left / right don't capture in the screenshots). They are the correct aspect though

Screenshots are quite useless in this case... Better have actual photos of the screen with bezels visible. (and used config) EDIT: and winuaelog.txt. Lets finally solve this..

[Vairn]

@Toni, I have the same issues as DamianD.
do you want a sample of his Config?
Or do you have a sample config setup?

[Toni Wilen]

Lets start with your current d3d9 (or d3d11 if it is the only working one) config: attach both logs, config and photo of screen. I'll make some test suggestions after checking them.

[Foebane]

I changed my configurations to D3D11, and I'm wondering if it requires any extra GPU power compared to D3D9 - I'd swear the framerate for some programs is lower with D3D11. I'm using an Intel Core i3 8100 with UHD 630 graphics (integrated only, no card).

EDIT: Never mind, I just compared the same moment from the same demo in both configurations, and they seem identical. A slight jerky scrolling problem I saw last night under D3D11 appears to have disappeared.