RUM-2903 fix: refresh rate vital for variable refresh rate displays when over performing #1973
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.
What and why?
Last time when we touched this area, we normalized the FPS relative to the expected rendering rate for variable refresh rate displays.
ie when a display is rendering at 30fps and expected rate is also 30fps, we report 60fps. This is because our backend only supports 60fps and renders useful indicators.
However, in some case, it has been observed that sometimes display renders quicker than expected.
ie when a display is rendering at 45fps and expected rate is 30fps, in this case normalization doesn't work and we go on to report 90fps which is not correct.
How?
Review checklist