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: uses 1st tracked controller instead of headset orientation (fix #5315) #5308

Merged
merged 9 commits into from
Nov 22, 2024

Conversation

DougReeder
Copy link
Contributor

Description:

When used with a headset capable of AR, the ar-hit-test component currently projects its ray from the headset, which is suboptimal UX when tracked controllers are available.

Changes proposed:

This change adds a new HitTest component, using the first tracked controller's targetRaySpace.

hit-testing has only been tested with a Quest 1 headset

@DougReeder
Copy link
Contributor Author

Also fixes bug #5315

@DougReeder
Copy link
Contributor Author

hit testing now also tested under Android 13 (on a Pixel 5)

@gydence
Copy link

gydence commented Dec 21, 2023

I can confirm that this fixes #5315 for me on multiple Android phones.

@dmarcos
Copy link
Member

dmarcos commented Nov 20, 2024

This needs rebase. Sorry for the wait. Should we use the controller (inputSource) that trigger the selectstart event vs the first we find?

@dmarcos dmarcos changed the title ar-hit-test: uses 1st tracked controller instead of headset orientation ar-hit-test: uses 1st tracked controller instead of headset orientation (fix #5315) Nov 22, 2024
@dmarcos
Copy link
Member

dmarcos commented Nov 22, 2024

Thanks!

@dmarcos dmarcos merged commit 3eadfd3 into aframevr:master Nov 22, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants