ar-hit-test turning enabled = off makes the entity "lose track"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
A-Frame Version: 1.4.2
Platform / Device: Android Moto g100, Moto Edge 40 Pro
Reproducible Code Snippet or URL: https://glitch.com/edit/#!/exciting-thankful-microwave
Turning enabled : false in the ar-hit-test component makes the entities lose track
Sorted this out by instead changing the target and src parameter after successfully placing the object on the ar surface.
Should the enabled parameter work?
https://glitch.com/edit/#!/exciting-thankful-microwave
Here you scan the floor, see a red reticle, tap on the screen and my object is spawned on the floor, in the "ar-hit-test-select" event I turn enabled false in the ar-hit-test, If i do it immediately you dont see the object appear, so I added a timeout of 2 seconds to do it, after that you can see the object "disappear" but its far off the camera at your left....}
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 ar-hit-test component behavior in the linked Glitch reproduction, especially the ar-hit-test-select event where enabled is set to false after placement. Verify whether disabling it makes the placed entity disappear or move out of view; done means the entity remains visible and tracked after hit testing is disabled.
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
- 35/100