Oculus Go controller shown too low

[jean-philippe-martin]

Description:

When using "laser-controls" on the currently-in-development version of aframe with an Oculus Go, the OGO model is shown on the screen as expected, but it is much too low - like our arms extend to our thighs and we hold the controller there instead of having the arm folded in a more natural pose.

In contrast, the GearVR controller model in version 0.8.0 is higher, in a more natural pose. That version doesn't have the Oculus Go controller model, though.

I haven't been able to test other controllers, so I don't know whether the problem is specific to the Oculus Go.

• A-Frame Version: master
• Platform / Device: Oculus Go
• Reproducible Code Snippet or URL:

<script src="https://rawgit.com/aframevr/aframe/master/dist/aframe-master.js"></script>
<a-scene  antialias="true" cursor="rayOrigin:mouse">
<a-entity laser-controls="hand: right"></a-entity>

Full code at:
https://glitch.com/edit/#!/aframe-laser-controls
demo at:
https://aframe-laser-controls.glitch.me/

[jean-philippe-martin]

Is there some way to raise it, a workaround?

[machenmusik]

Sounds like something may be causing issues with the arm model, in src/components/tracked-controls.js
Question, if you explicitly add a camera e.g. using , does the observed behavior change?

[jean-philippe-martin]

I'm sorry @machenmusik, using what ? It looks like github ate your tags.

[wmurphyrd]

I've noticed this also when testing with Vive Focus for our incoming vive-focus-controls component. In the laser controls example scene on master, the controller is located correctly, but the camera is far too tall.

When using the focus in our project, on 0.8.2 with a camera rig structure, the location of the camera and controller are correct.

[machenmusik]

That was supposed to be using a-camera, I think. I am guessing that changes to the way position and user height are now managed by aframe may have messed up arm model behavior when not in a camera rig

[dsinni]

It's not limited to the arm model, though. The camera cursor appears pretty low as well (you have to look down to see it), since the camera Y is too high. The height of the arm model is quite possibly accurate when placed within the rig.

[machenmusik]

I think this may be #3748

[lerabot]

I can only confirm this. Been trying to messa round with the armModel parameter. It actually just makes it worse.

[ngokevin]

should be fixed

[binzume]

I also encountered the same problem.
It seems that both of A-Frame and Three.js(WebVRManager) are adding user height.

three.js: https://github.com/mrdoob/three.js/blob/3148b9e3783ecf2eeaa3d1ca7242d6bcf082fac5/src/renderers/webvr/WebVRManager.js#L262

[lerabot]

Would this also be why the "cursor" doesn't work with the oculus go? It's always to low and won't track the camera at all.

[dsinni]

Just wanted to chime in to say that this is still an issue in
fce54481970c5f34a3fe9fd2c130dcfc4e3bdb1b as 0.9.0 testing is underway.

The camera height is still too high on the Go.

[stlewis]

I've been investigating, and the breaking changes for both the cursor and the controls, (Go and GearVR), were introduced at e0c8ff7. There's a lot of code in that commit and I'm still parsing through to see if I can find the specific culprit, but if anyone else wanted to put a pair of eyes on it, that's where to look.