Remove last vestiges of input latency from Duke3D and RR main game loops. #21
Conversation
This file contains 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
…ops. - Hack code to break loop early removed. If game code is running slow, that's not the fix. - Get input and fill the input_t struct in same loop as G_DoMoveThings(). - Remove unnecessary do/while (0) loop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The improvement is very subtle but I can definitely tell the difference. Might be less noticable at refresh rates higher than 60Hz (it's all I have until the AUD gets better).
Some notes on the 'hack code', it might have made sense when it was committed, but when I altered to loop to run as fast as it could on my Core i7 4770k, the game easily ran 5-6 times faster than it should have with vsync on, and many magnitudes faster with vsync off. The shotgun unloaded 50 shells in about 2.5 seconds. It's just not needed.