Debug text example: render fps and frame time #978
Merged
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
ambeeeeee
reviewed
Dec 2, 2020
|
Looks good to me (once you apply @memoryruins's suggestion and fix formatting) |
|
Not sure how I missed the formatting change. I tend to run |
I guess you meant @amberkowalski 's suggestion? I thought the change to a |
|
Nope I meant @memoryruins' suggestion (the with query) |
Closed
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.
I saw @cart's PR #972 and was curious about how much it improved the impact of text rendering on frame rate in general so that one can have a HUD displaying frame time and frame rate. The answer (on a MacBook Pro 16" with Radeon Pro 5500M) is... before:
...after:
Note that I disabled vsync in the example to see how fast it can really go! :)