AFrame tracked-controller glitches for screen input
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description: When using touchscreen XR input, the tracked controller is shown at the touch location
- A-Frame Version: 49b3f03 (master, Oct 21 2019)
- Platform / Device: Android
- Reproducible Code Snippet or URL: https://klausw.github.io/aframe/examples/showcase/tracked-controls/
How to reproduce:
- use ARCore-compatible phone with Chrome 79, "WebXR AR Module" enabled in chrome://flags
- enter AR mode
- drag the finger around on the screen
It draws what appears to be the inside of the controller hand around the touch point:
A possible fix would be to set the controller invisible if session.inputSources[i].targetRayMode is screen.
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 with the tracked-controls example at https://klausw.github.io/aframe/examples/showcase/tracked-controls/ and inspect how session.inputSources are handled. Reproduce the issue on an ARCore-compatible Android phone with Chrome 79, then verify that screen target-ray input no longer renders a tracked controller while other controller input remains visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100