This repository was archived by the owner on May 13, 2025. It is now read-only.
Disabled v-sync, capped FPS to 60 - #298
Open
jaschutte wants to merge 1 commit into
Open
Conversation
Open
Contributor
|
Is there a reason this issue needs to be worked around in advance of resolving it directly? And, is a capped framerate necessarily more comfortable than the jittering? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
Disabled v-sync and used an FPS cap of 60 instead.
This is done to combat the stuttery behavior the game displays as higher refresh rates. This stuttering only appears on frame rates higher than 60, not lower than 60. Having the FPS being capped at 60 effectively eliminates the issue. Note that v-sync does not help, as monitors can have higher refresh rates than 60, and thus the character still stutters.
Disclaimer
This isn't exactly a fix, but rather a workaround. We should get behind the core of this issue some day, but for now this would suffice.
Issue(s)
Closes #293 and possibly #268