You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is very nice to see a detail document, it help a lot to make the IVRVirtualDisplay clear.
For now the interface don't contain pose (comparing to IVRDriverDirectModeComponent), which is needed in warpping.
BTW now i facing the Jitter when using IVRDriverDirectModeComponent, its would be nice to see a similar document about IVRDriverDirectModeComponent. For example, IVRDriverDirectModeComponent not provide a way for driver to submit vsyns time so how IVRDriverDirectModeComponent know the vsync time ?(my wild guess is by the return time of IVRDriverDirectModeComponent::present?
The text was updated successfully, but these errors were encountered:
For IVRDriverDirectModeComponent, you can send vsync events by setting the following property: Prop_DriverDirectModeSendsVsyncEvents_Bool
Then calling VRServerDriverHost()->VsyncEvent with the time in seconds until the next vsync, before returning from Present.
For pose, it isn't clear which pose should be passed, or what space it should be provided in (particularly since drivers can only get 'raw' tracking poses to compare against).
Hello everyone,
When i setting Prop_DriverDirectModeSendsVsyncEvents_Bool to True.
This seems to produce a hidden vertical sync time (approximately 16.6ms), which means that the present function is called every 16.6ms (60hz).
I tried adding a manual insert vsync, for example, calling vr::VRServerDriverHost()->VsyncEvent(0) every 13.3ms (75hz), but the actual situation is that he becomes 75 + 60=135hz, which means the default 60hz still exists.
When i setting Prop_DriverDirectModeSendsVsyncEvents_Bool to False. After each frame is rendered, it will be directly presented. The frame rate is not fixed. This is not what I want.
It is very nice to see a detail document, it help a lot to make the IVRVirtualDisplay clear.
For now the interface don't contain pose (comparing to IVRDriverDirectModeComponent), which is needed in warpping.
BTW now i facing the Jitter when using IVRDriverDirectModeComponent, its would be nice to see a similar document about IVRDriverDirectModeComponent. For example, IVRDriverDirectModeComponent not provide a way for driver to submit vsyns time so how IVRDriverDirectModeComponent know the vsync time ?(my wild guess is by the return time of IVRDriverDirectModeComponent::present?
The text was updated successfully, but these errors were encountered: