Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Libretro] Vulkan crashes with exclusive fullscreen mode #15381

Open
4 of 5 tasks
BParks21 opened this issue Feb 7, 2022 · 6 comments
Open
4 of 5 tasks

[Libretro] Vulkan crashes with exclusive fullscreen mode #15381

BParks21 opened this issue Feb 7, 2022 · 6 comments
Labels
Libretro Issue on Libretro but not all ports.

Comments

@BParks21
Copy link

BParks21 commented Feb 7, 2022

Game or games this happens in

Any

What area of the game / PPSSPP

Boot.

What should happen

Core should work with vulkan renderer in exclusive fullscreen mode. Works in borderless window and windowed mode.

Logs

No response

Platform

Windows

Mobile phone model or graphics card

GTX 1080ti

PPSSPP version affected

Latest libretro core

Last working version

Not sure if it ever worked

Graphics backend (3D API)

Vulkan

Checklist

  • Test in the latest git build in case it's already fixed.
  • Search for other reports of the same issue.
  • Try resetting settings or older versions and include if the issue is related.
  • Try without any cheats and without loading any save states.
  • Include logs or screenshots of issue.
@unknownbrackets unknownbrackets added the Libretro Issue on Libretro but not all ports. label Feb 7, 2022
@BParks21
Copy link
Author

BParks21 commented Feb 7, 2022

Maybe related? #10784

@BParks21
Copy link
Author

BParks21 commented Feb 7, 2022

Ok I've discovered that this only happens when RA refresh rate is set to anything but 60hz in the output section of RA's video settings. Having RA set to 165hz or 120hz PPSSPP crashes in fullscreen on boot. With it set to 60hz it does not crash with vulkan on boot.

@metagondria
Copy link

metagondria commented Dec 28, 2022

Ok I've discovered that this only happens when RA refresh rate is set to anything but 60hz in the output section of RA's video settings. Having RA set to 165hz or 120hz PPSSPP crashes in fullscreen on boot. With it set to 60hz it does not crash with vulkan on boot.

I happen to have an 165hz 1440p Monitor..

And, going 60hz all the way to work arround it won't cut it !!

i have tried 50 and 60hz output in RA , and as soon you Toggle-fullscreen it crashes !! Starting in fullscreen however, won't crash RA... But going from full to window , boom → crash regardless of the refresh rate setting!

so then i have tried to reproduce the problem by setting everything to 60hz, desktop refresh rate included .. and the same keeps happening !!

Something happends when toggle / switch to fullscreen or back to windowed state !! And only with vulkan renderer, OpenGL isn't affected by this !!

My Gpu is an RX-6600 Amd → Win10x64 Driver 22.11.2

Cheers,

@genpfault
Copy link

genpfault commented Jan 3, 2023

For me the fix is to set the Windows scaling factor ("Make everything bigger" in Settings) to 100% (down from 150% in my case).

Sadly, setting retroarch.exe's "High DPI scaling override" compatibility setting to "Application" doesn't work, I have to set the overall OS scaling :(

Windows 10 with a Radeon 5700, RetroArch 1.14.0, onto a 1920x1080 TV.

@gouchi
Copy link
Contributor

gouchi commented Jun 2, 2024

@BParks21 @metagondria @genpfault Is it still an issue using latest update as there was some update about context cleanup ? Thank you.

@BParks21
Copy link
Author

BParks21 commented Jun 2, 2024

It's better. RA will crash if I press F to go to window mode too quickly after launching a PSP game. If I wait a little longer then it doesn't crash RA. Or if I go in and out of fullscreen too quickly back to back it will crash. So doesn't seem completely stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Libretro Issue on Libretro but not all ports.
Projects
None yet
Development

No branches or pull requests

5 participants