You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested Three.js XRControllerModelFactory with the extension. With the extension (webxr-polyfill.js) the controller (grip) or ray direction looks weird as the screenshots below.
On the emulated OculusGo of the extension the controller looks at different direction from the ray's while on real OculusGo the controller and ray seems to look at the same or similar direction.
(FYI, Real Oculus Go out of browser. Looking different even a bit further from in VR mode??)
I haven't looked into other than OculusGo, but I think other devices may have the same issue.
my guess and question
I guess this issue may be from grip/targetRayTransform numbers defined in GamepadMapping.
According to @jsantell, these numbers seems from this commit by @jacobcdewitt. So question, how are these numbers determined? And are these numbers looking correct?
The text was updated successfully, but these errors were encountered:
Hi all.
Background
I'm making WebXR Emulator Extension which imports webxr-polyfill.js.
Problem
I tested Three.js XRControllerModelFactory with the extension. With the extension (webxr-polyfill.js) the controller (grip) or ray direction looks weird as the screenshots below.
On the emulated OculusGo of the extension the controller looks at different direction from the ray's while on real OculusGo the controller and ray seems to look at the same or similar direction.
Three.js XRControllerModelFactory + WebXR Emulator Extension + Emulated Oculus Go in VR mode
Three.js XRControllerModelFactory+ Real Oculus Go in VR mode
(FYI, Real Oculus Go out of browser. Looking different even a bit further from in VR mode??)
I haven't looked into other than OculusGo, but I think other devices may have the same issue.
my guess and question
I guess this issue may be from
grip/targetRayTransform
numbers defined inGamepadMapping.
According to @jsantell, these numbers seems from this commit by @jacobcdewitt. So question, how are these numbers determined? And are these numbers looking correct?
The text was updated successfully, but these errors were encountered: