Issues with Fullscreen capping FPS at 60 on monitor that was selected in osu!lazer at startup #28106
-
I've been experiencing an issue with osu!lazer today, no matter what renderer I choose and whatever limiter I choose on my MSI Optix MAG274QRF-QD it will cap at 60 fps as long as I'm on fullscreen. (Please note that my monitor is set to a refresh rate of 165 Hz, so even with VSync this would be wrong) Restarting the computer didn't help and switching to Borderless Windowed fixes the issue. I also tested to move the game to another monitor which works fine and the fps cap is set as it should be. I'm running a system with a AMD Ryzen 9 7950X and a AMD Radeon RX 7900 XTX and the version for my AMD Adrenalin Software driver is 24.4.1. I've played lazer on this monitor already and it was never an issue before 24.4.1, so it was fine on 24.3.1. I added the logs here if that is maybe something that is in the control of osu!lazer itself but I doubt it so far. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
In addition to everything there are some other behaviour based on the renderer when being in Windows / Borderless with no Frame limiter (only on this one monitor):
After some more testing I found out that the issue only appears on the monitor that is configured once the game is started. Changing the monitor fixes the issue. However going back to the first monitor will result in a cap of 165 fps (it shows 1000 fps cap in osu - using any Direct3D 11 implementation) in Borderless / Windows and on Fullscreen it will result in a cap of 60 fps (shows a 1000 fps cap in osu again). |
Beta Was this translation helpful? Give feedback.
-
Okay so I downgraded to 24.3.1 and my issue still persists, so this has been the case since I last updated lazer so I would say it's not only related to my Driver. |
Beta Was this translation helpful? Give feedback.
-
I was able to fix the issue, for some reason the driver update enabled FPS Target control somewhere deep in the driver, disabling it fixed it. |
Beta Was this translation helpful? Give feedback.
I was able to fix the issue, for some reason the driver update enabled FPS Target control somewhere deep in the driver, disabling it fixed it.