Buttons and axes incorrectly mapped in windows-motion-controls
Open
Nobody has claimed this yet.
help wanted (easy)
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
- A-Frame Version: 1.0.4
- Platform / Device: Firefox / Windows MR
In the WebVR mapping (which is what's currently being used with Firefox), controller button id zero is incorrectly given as "thumbstick" when it should be "trackpad".
The trackpad x, y position is also incorrectly mapped to the thumbstick position, so the trackpad acts like a thumbstick and the thumbstick itself is inoperative.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the windows-motion-controls WebVR mapping used by Firefox on Windows MR and inspect how controller button id zero and the trackpad x/y values are assigned. Done means button zero is exposed as trackpad, trackpad coordinates no longer drive the thumbstick, and the thumbstick mapping works correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ar-vr-xr
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100