KhronosGroup / KhronosGroup/OpenXR-Docs
OpenXR's Controller Poses do not cover the necessary information
- Dominant language
- Python
- Stars
- 181
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
I had originally posted this on Reddit and a suggestion was made to create an issue for my recommendations here.
I've read the docs and have been working on converting some advanced VR avatar body systems to OpenXR.
I've found that the intended poses provided by the OpenXR spec (Grip and Aim Pose) aren't enough to be usable for what they are intended for.
The Aim Pose of course is useful for what's intended, but the Grip Pose is intended to allow positioning the in-world object correctly and that is not actually possible with the provided data. It is very much controller specific, which is not viable for supporting future hardware and hardware that the developer doesn't have access to.
I have a solution to this as described in my video explaining the issue.
Please see the following video that explains the issue in detail.
It is my understanding that this video may have already been discussed in a KhronosGroup call, but if not here is the link.
[OpenXR Discussion Video](https://www.youtube.com/watch?v=g-zupOaJ6dI)
An additional point to add to the described "Palm Pose" would be to place it parallel to center palm, but instead of in the centroid, place it behind the Index finger, where the Index finger's first joint begins.
Please inform me if there is a better place to make these kinds of requests.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the OpenXR specification sources and the linked OpenXR Discussion Video, then check the existing Grip and Aim Pose definitions. The issue describes a proposed Palm Pose and additional placement guidance, but does not identify a file, test, or agreed specification change to use as the completion target.
Written by the indexing model from the issue text.
Assessment
- Domain
- ar-vr-xr, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100