Camera's child entities won't fix to camera in vr mode (in mobile)

[fzaiatz]

Cursor or any other camera's child entity doesn't seem to respect fixed position when in vr mode (this is working as expected in 0.8.2)

• A-Frame Version: master (19/9/18)
• Platform / Device: Safari/Chrome (iOS 11, iOS 12)

[jerichozis]

Yeah, just noticed that cursor is broken.

[ngokevin]

Might be because in VR mode, it's the inner camera pose that is getting changed rather than the entity itself...worth checking out.

[dmarcos]

This is a side effect of the new VRManager API. The camera passed to the render method on of THREE.Scene is not the camera used to render on VR mode and hence its transforms don't carry on to the children of the true camera.

[ngokevin]

Gross workaround is just add the entities under cameraEl.getObject3D('camera') via JS (move the object3D over), or copy the cameraEl.getObject3D('camera') position/rotation to another entity.

[machenmusik]

Can't the pose/orientation copy be done by the framework, for compatibility? Although if XR manager will behave differently than VR manager, maybe worth going to XR now if there is already breakage anyway?

[ngokevin]

What entity do you copy it to? Three.js requires to manipulate the camera, and had to fight a bit to even be able to send that data up to aframe. If you copy to the camera entity, the transforms will stack.

Moving completely to XR now doesn’t make much sense for now . Will want to support both. XR API is going to take a while to roll out, and from what it looks, it’s going to have less features and capabilities than the current API. Most likely will want to have aframe manage the vr/XR rather than three.js soon. Doesn’t offer enough control

[machenmusik]

Sorry, I thought from your description that it was a different camera and transforms wouldn't stack so it would be easy.

Yeah, WebXR may lag for a while, and it seems to me that the switch away from VRControls and A-Frame being in control isn't working out so well at the moment

[ngokevin]

#3820