Enable VRChat gesture support by changing EVRSkeletalTrackingLevel to Full #2283
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
Contributor
|
When it comes to VRChat compatibility, the VRC devs have provided documentation on exactly how they're expecting controllers to behave when switching between hand tracked and controller modes: https://creators.vrchat.com/platforms/pc/steamvr-drivers/#hand-virtual-controller |
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.
Small change, already tested by multiple people, works.
May cause gestures to trigger when using controllers, not an issue in VRChat with pico(quest) controllers.
This can be mitigated as so but I don't have the time to implement this:
"In the case of supporting switching between finger tracking and controllers, the way to make it so that a driver's skeleton data, as available to the application over the API is clearly identifiable as being suitable for interactions or not, is to have the driver define two different controller types, one for controllers that always initializes its skeleton as either partial or estimated, and one for finger tracking that always initializes its skeleton as full, and switch between them when the source input provider switches between controller and hand tracking "