Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding client-side prediction entries to the DirectMode and non-Direc… #399

Merged
merged 1 commit into from
Apr 21, 2016

Conversation

russell-taylor
Copy link
Contributor

…tMode RenderManager configs assuming that they are being applied to an HDK.

Varies the prediction interval for landscape/portait and direct/nondirect.
Adds expected HDK sensor delay to all of them.

…tMode RenderManager configs assuming that they are being applied to an HDK.

Varies the prediction interval for landscape/portait and direct/nondirect.
Adds expected HDK sensor delay to all of them.
@rpavlik
Copy link
Member

rpavlik commented Mar 24, 2016

Do the prediction amounts in here account for the fact that there's already prediction being done server-side? (I ask since you mention "expected HDK sensor delay") Also, how will this work with the positional tracker once I get that reporting velocities too?

@russell-taylor
Copy link
Contributor Author

The prediction amounts assume no server-side prediction. The sensor delay is added to the common prediction interval, which is used for both eyes. Positional prediction already in the code but not yet tested in combination with orientation.

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

Successfully merging this pull request may close these issues.

None yet

2 participants