Open
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replaces the VSync options with a general-purpose FPS limiter to reduce the game's CPU/GPU utilization and to make speedrunning tricks consistent. Users can set their FPS to be limited by full vsync, adaptive vsync, unlimited, 60fps, 120fps, etc.
Tried a couple ideas for implementing this but found this frame skipping method to feature the most stable FPS limit (little to no deviations up or down). In my testing, the frame skipping appears to have a negligible performance impact compared to more
love.timer.sleep-based solutions, which I found to be either very broken (running too fast/slow) or unstable (high variation in frame timing).