-
Notifications
You must be signed in to change notification settings - Fork 553
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
[BUG] Refresh rate drops when the game is minimized (alt-tabbed) #2828
Comments
does passing |
|
does setting |
No, it doesn't look like it - even when I start a level. I mean, the game is progressing in the background as it should be, but my monitor is still stuck at 49 Hz. |
i have the slight suspicion this might be windows' doing for minimized programs |
I think you might be on to something here. I don't have a lot of other games installed, but I do have one that I know supports Vulkan: The Talos Principle (1). And when it's minimized, the observed behavior does indeed appear to be similar, albeit not entirely the same: according to the OSD, the refresh rate fluctuates wildly between 144 Hz and somewhere around 50 Hz. The impact on smoothness is also noticeable, but perhaps a bit less than with GZDoom. And changing the backend to D3D11 makes it go away, just like it does when switching to OpenGL (ES) in GZDoom. So, not sure about Windows, but could it be a graphics driver issue then, maybe?
Thanks, but that didn't change anything, even after a restart.
Now, there is one other thing this your other thing prompted me to check: If I alt-tab out of the game and press Win+D, the refresh rate goes to the usual 144 Hz until I unminimize GZDoom and then alt-tab again. (Interestingly, TTP seems to crash every time I do that, and again only when using Vulkan.) |
https://learn.microsoft.com/en-us/windows/win32/api/timeapi/nf-timeapi-timebeginperiod I have a feeling it is related to Windows 11's new timer behavior for minimized apps. |
seems like the new behavior can be disabled |
I've got a report from another person who's running the same GPU driver but an older OS (Windows 10 Pro 22H2 build 19045.5131) - he could not reproduce the issue. Quite possible that it only appears on Windows 11, then. |
Perhaps unrelated, but I've also recently noticed that alt-tabbing out of GZDoom and then back in might introduce a significant amount of in-game audio lag when I'm using my Bluetooth headset. I understand that some latency with Bluetooth is unavoidable, but sometimes it gets so high (at least half a second by the feel of it) that it becomes downright annoying. Restarting sound does not help at all, only alt-tabbing again does, but not all the time. Could it also be due to this Windows timer behavior? |
GZDoom version
4.13.2 and 4.14pre-89-g99c058d16
Which game are you running with GZDoom?
Doom 2
What Operating System are you using?
Windows 11
Please describe your specific OS version
Windows 11 Pro 23H2 (build 22631.4460)
Relevant hardware info
NVIDIA RTX 4090
Have you checked that no other similar issue already exists?
A clear and concise description of what the bug is.
With the latest NVIDIA driver (v. 566.14 as of now) and a G-Sync Compatible monitor with a variable refresh rate, the latter appears to drop severely when Alt-Tabbing out of the game window. For example, my monitor's OSD shows that the refresh rate is 49 Hz (!) when the game is minimized. This is highly noticeable especially compared to the default refresh rate of 144 Hz, making all animations in the OS GUI, like scrolling and even cursor movement, feel very choppy.
Note that this happens regardless of whether the game is paused or not, and it isn't even necessary to start a level in order to witness this effect. But it only happens in fullscreen mode, not windowed. As long as GZDoom is running in windowed mode and the window is brought out of focus, the refresh rate stays at maximum.
This issue manifests only with the Vulkan backend. OpenGL and OpenGL ES are not affected.
Steps to reproduce the behaviour.
Explain how to reproduce
Your configuration
Provide a Log
https://gist.github.com/Player701/128e9c690adcfc64f5daadf98db149e6
The text was updated successfully, but these errors were encountered: