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

Alt tabbing out of vulkan games result in black screen #116

Open
BiRooT opened this issue Jan 19, 2022 · 1 comment
Open

Alt tabbing out of vulkan games result in black screen #116

BiRooT opened this issue Jan 19, 2022 · 1 comment

Comments

@BiRooT
Copy link

BiRooT commented Jan 19, 2022

Hey,

First of all, thanks for this usefull program :)

I would like to bring your attention to the fact that it seems that my black screen issue when alt tabbing out of Vulkan games comes from VibranceGUI 2.3.1.1 (seems your last stable version).
I have an AMD GPU (RX 5700 XT), when I play to DirectX games, I don't have any problem, if I launch a Vulkan game (Red Dead Redemption 2 at least, I just have this game running Vulkan API to test), after one or several alt tab, display driver seems to crash (I can continu to hear game sound or teamspeak users voice).

  • If I reset my PC, it reboot and display is fine.
  • If I don't reset my PC after this black screen, few seconds later, I hear this windows sound like I unplug a USB key, screen remain black so I'm forced to reset my PC, and after reboot, display driver don't load, and if I force launch radeon software, I'm getting an error (don't remember what) but I need to reinstall radeon software.

Multiple radeon drivers tested, they all have the problem.
I tried without VibranceGUI launched, no problem at all.

I use function which allows to change the vibrance according to the program (so according to RDR2).
If I remove program from the list and I set a vibrance for system-wide (Windows vibrance level), I don't have this black screen issue.

Thanks for your help ;)

@juv
Copy link
Owner

juv commented Mar 26, 2022

Hi,

thanks for creating this issue. Unfortunately, the AMD version of vibranceGUI is no longer maintained because the contributor for the AMD portion of the code has lost interest. Because I do not have access to an AMD gpu, this will be hard to test and find a solution for. It's unlikely that this can be resolved anytime soon if not someone else steps up and tries to implement a bugfix for this.

@juv juv added the help wanted label Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants