Skip to content
This repository has been archived by the owner on May 15, 2020. It is now read-only.

some issues with hand-controls and oculus-touch-controls #10

Closed
giordyb opened this issue Mar 4, 2017 · 4 comments
Closed

some issues with hand-controls and oculus-touch-controls #10

giordyb opened this issue Mar 4, 2017 · 4 comments

Comments

@giordyb
Copy link

giordyb commented Mar 4, 2017

I'm not sure if it's an issue with your component or with aframe 0.5.0 in general but I'm adding this issue here since it affects your component:

  • both hand-controls and oculus-touch-controls require the raycaster to be set.
    to get the basic example to work I had to add
    raycaster="objects: #sphere" to the entity

  • hand-controls: when I click the sphere the "click" event gets called twice instead of once. this does not happen with the oculus-touch-controls.

@rxl881
Copy link
Contributor

rxl881 commented Mar 9, 2017

I'm also seeing the same problem with the raycaster needing to be set when using vive controllers. giordyb's workaround of adding the raycaster explicitly on the entity worked for me.

@pinnareet
Copy link

I'm not sure, but I think it may be a bug with aframe raycaster implementation where they check for objects being null to intersect with everything, but actually pass an empty string {''} as the default.

@bryik
Copy link
Owner

bryik commented Mar 16, 2017

With hand-controls, I didn't need to add the raycaster explicitly but the "click" event was called twice instead of once. Considering it doesn't happen with vive-controls, I'm not sure the problem is with controller-cursor.

@ngokevin
Copy link
Collaborator

It's a bug with A-Frame aframevr/aframe#2379

@bryik bryik closed this as completed May 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants