Display real FPS as a fallback if GPU time information is not available #99301
+20
−8
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
Calinou
added
bug
topic:editor
cherrypick:4.3
Calinou
force-pushed
the
editor-fps-gpu-time-fallback
branch
from
48c6d96 to
a1ab049
Compare
This fixes FPS being reported as 100000 on the web editor and on other platforms/renderers where GPU time information isn't available.
Calinou
force-pushed
the
editor-fps-gpu-time-fallback
branch
from
a1ab049 to
467a401
Compare
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.
This fixes FPS being reported as 100000 on the web editor and on other platforms/renderers where GPU time information isn't available.
Preview