Open
Conversation
Owner
|
Instead of having separate paths for estimated and real skeletal summaries, I think we can just
|
Contributor
Author
As in, cache the openvr skeleton each frame and do a unified summary calculation from that? |
Owner
|
Yes, but don't automatically get the skeletal state each frame. Just when necessary, and don't try to calculate it more than once a frame. |
This comment was marked as off-topic.
This comment was marked as off-topic.
5fedcec to
a66529f
Compare
1 task
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ports over the skeletal summary from OpenComposite to make gestures work in VRChat on index controllers. I'd like to do this better in the future (and implement splay), but this at least gets things working.