Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ar-hit-test fails if controller button released before reticle is placed #5315

Open
DougReeder opened this issue Jun 21, 2023 · 2 comments
Open

Comments

@DougReeder
Copy link
Contributor

Description:

  1. click AR button to start AR mode
  2. While ensuring the headset is never pointed toward a hit-test surface, press and release the select button (usually the trigger).

Expected result: reticle will still appear when headset is then pointed toward a hit-test surface
Actual result: reticle does not appear when headset is then pointed toward a hit-test surface

@dmarcos
Copy link
Member

dmarcos commented Jun 21, 2023

I don't think this was ever tested on headset. It was deved for handheld. QA and PRs super welcome

@gydence
Copy link

gydence commented Dec 20, 2023

I am also experiencing this on multiple Android phones.

gydence pushed a commit to gydence/aframe that referenced this issue Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants