Feature: load / save max fps value in config#24
Open
YALdysse wants to merge 1 commit into
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.
Hi, @AltronMaxX.
Until a solution is found to the physics bugs at high FPS, I suggest the following partial workaround. I found a commit that implemented the reading of the maximum frame rate parameter and its subsequent writing to the configuration file. This way, users will be able to raise the FPS limit to a level where physics distortions are minimal, whilst still achieving a smooth display.
I am not the author of the commit. Here is the link to the commit.
I propose merging this feature into the main branch, as I consider this change to be important.
Together, we can make the reVC engine even better!