cube: Fix GOOGLE_display_timing desired-present-time calibration. #1177
+1
−1
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
as the name says, we're calculating what the previous present's desired time should have been, which will have IPD added for the next_present_id's presentation. So for example, if we are processing the last presented frame's actualPresentTime, our multiple should be 0, not 1. Now the demo properly locks to 60fps for a 1.0 IPD on my 60Hz display.
|
Author anholt not on autobuild list. Waiting for curator authorization before starting CI build. |
1 similar comment
|
Author anholt not on autobuild list. Waiting for curator authorization before starting CI build. |
charles-lunarg
approved these changes
Nov 14, 2025
|
CI Vulkan-Tools build queued with queue ID 579089. |
|
CI Vulkan-Tools build # 1859 running. |
|
CI Vulkan-Tools build # 1859 passed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
as the name says, we're calculating what the previous present's desired time should have been, which will have IPD added for the next_present_id's presentation. So for example, if we are processing the last presented frame's actualPresentTime, our multiple should be 0, not 1.
Now the demo properly locks to 60fps for a 1.0 IPD on my 60Hz display.