-
Notifications
You must be signed in to change notification settings - Fork 49
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
VibranceGUI manually reseting my monitor refresh rate down #98
Comments
I would like to report the same problem. My main monitor is 144 hz and, with VibranceGUI opened, it restarts my nvidia configuration to 60 hz, no matter how many times I change it. I'm using latest Nvidia drivers nowadays and VibranceGUI 2.3.1.1. |
Does this also happen when you select the "Never change resolutions" checkbox? edit: |
Little late but I have the same problem. I'm using just 1 monitor. |
@sgraewe @DavidCorral94 @akej111 can you check if this is still happening on the most recent vibranceGUI version and if yes, please make sure to verify if enabling the |
Hi all, can you please take a look at this new beta version i have built based on this PR: #140 You can download the pre-release .exe here: |
Currently having an issue with Valorant
Steps that happen
The same happens if I try to change the refresh rate via Nvidia control panel too. The strange thing is Valorant runs at the original 165hz if I tab back in. But once I tab out or close the game, it's hard stuck at 60 until I tab back into Valorant, or restart my computer and manually set the refresh rate back.
I found this reddit thread where a user also had a similar issue, and when I disabled my VibranceGUI I was finally able to change the refresh rate without it getting reset. I suspect this has to do with the fact that my resolution is changing when I go into Valorant and come out (1440p native to 1080 ingame) as I hadn't run into this issue until I changed res's (although were times where I can tab out just fine)
Running a i7-8700 and a 1060, with latest drivers from Nvidia
The text was updated successfully, but these errors were encountered: