-
-
Notifications
You must be signed in to change notification settings - Fork 4
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]: FPS unlocking not working perfectly #34
Comments
Can confirm I can replicate this now, sort of. I've done some testing and it looks like only windowed mode actually works properly at up to 240fps for me. Borderless and fullscreen work correctly only with Special K, but without it, they presumably vsync to 120fps. So when I did all my testing for this I was either using windowed mode for quickly going back and forth. Then when I actually played the game I used Special K, so I didn't catch this bug. They must be doing something odd in their borderless/fullscreen mode. For now as a workaround I'd recommend trying out Special K as hopefully that will work for you also. At least in the meantime until I can look into this further. Edit: Did more testing and it won't uncap in windowed now. But it does uncap in all 3 display modes when alt+tabbed. Bizarre. |
@GoLdEnSuNnN Try disabling G-Sync/Freesync in your driver control panel for this game. That seems to sort it on my end. |
Disabling gsync not working. Windowed mode also 180fps. |
Hmm not sure what's happening on your end then. If you force Vsync off in your driver control panel for the game does it work at all? I think what's happening is that the game has probably Vsync on in fullscreen/borderless regardless of the setting. |
Issue Summary:
FPS unlocking not working perfectly. Stuck at 180FPS which is refreshrate of the monitor. A friend has same issue with 165fps for 165Hz.
Vsync is off. Tried borderless and windowed. Even when fullwindow, this game somehow can limit the desktop framerate with it.
GBFRelinkFix & Game Version Numbers:
Tried 1.06 and 1.07, with 1.05 GAMEversion.
The text was updated successfully, but these errors were encountered: