Wrong position with AFrame 1.0.4 and Oculus Quest

[rotoglup]

I've found out that, when walking around using an Oculus Quest, the teleport location is off when the user walks far from the starting physical location (in track space).

When trying the original TakashiYoshinaga's Quest Demo it works fine, using AFrame v0.9.2.

I remixed the same example to use AFrame v1.0.4, and it exhibits the problem :

• enter VR mode
• walk one or two meters
• teleport, to see the location being off

Being new to AFrame, I may be wrong, but it seems that AFrame 1.0.4 always return [0,0,0] when querying the teleportOrigin position using getWorldPosition :

aframe-teleport-controls/index.js

Line 313 in d5ed392

teleportOrigin.object3D.getWorldPosition(teleportOriginWorldPosition);

[randytayler]

I'm seeing this too; did you ever find a solution, @rotoglup ?

[rotoglup]

@randytayler alas no, I did not have the time to fix this, I sticked to AFrame v0.9.2 where this component worked...

[AliKarpuzoglu]

can confirm this on the vive, too