`glTF`/`glb` models not raycastable in Oculus Go (`laser-controls`)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
It appears that glTF and glb models are not raycastable within Oculus Browser (perhaps others) on Oculus Go, while using laser-controls.
This works on desktop with the cursor component using the same raycaster="objects: [data-clickable];".
This makes it pretty difficult to obstruct raycasting with structures, etc.
Thanks, and keep up the great work!
- A-Frame Version:
0.9.0 - Platform / Device: Oculus Browser on Oculus Go (perhaps others)
- Reproducible Code Snippet or URL:
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 reproducing the issue on Oculus Browser on Oculus Go with A-Frame 0.9.0, using laser-controls, glTF or glb models, and raycaster="objects: [data-clickable];". Compare the laser-controls behavior with the desktop cursor component. Done means the models can be raycasted and structures can obstruct raycasting as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100