Skip to content
This repository has been archived by the owner on Nov 19, 2023. It is now read-only.

Use predicted frametime as a bevy time in the render graph #6

Open
blaind opened this issue May 30, 2021 · 0 comments
Open

Use predicted frametime as a bevy time in the render graph #6

blaind opened this issue May 30, 2021 · 0 comments

Comments

@blaind
Copy link
Owner

blaind commented May 30, 2021

From OpenXR docs:

The engine simulation should advance based on the display time. Every stage in the engine pipeline should use the exact same display time for one particular application-generated frame. An accurate and consistent display time across all stages and threads in the engine pipeline is important to avoid object motion judder. If the application has multiple pipeline stages, the application should pass its computed display time through its pipeline, as xrWaitFrame must be called only once per frame.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant