You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Thursday, May 14th 2020, 12:31am

Thumbsticks on Oculus Touch Controls no longer function in Oculus Browser after its update to WebXR only.

The ability to use the thumbsticks on the Oculus Quest controller to allow the viewer to turn or 3d movement within a depthmaped panorama is no longer possible through the Oculus Browser on the Oculus Quest after the latest update of the Oculus Browser which now only supports WebXR. The thumbsticks do still work in the Firefox Reality browser on Oculus. This krpano image works with thumbsticks in Firefox Reality, but not Oculus Browser: https://3d-360.com/gigakrindex.php?width…=218403&fov=360

The thumbsticks also do not work with the krpano examples through Oculus Browser on Quest https://krpano.com/releases/1.20.6/viewe…tour/index.html

I have tested and WebXR itself still has the ability to use the thumbsticks in the Oculus Brower, so this is something to do with krpano's implementation. This page works on Oculus browser through WebXR to see controller states https://immersive-web.github.io/webxr-sa…ller-state.html

This problem seems to be an issue with krpano's use of WebXR and not WebXR itself.

This post has been edited 1 times, last edit by "odysseyjason" (May 20th 2020, 8:46pm) with the following reason: more clarity on problems with url's to example pages


2

Thursday, May 21st 2020, 12:29am

Hi,

yes, that's due the WebXR API.

The krpano WebVR plugin was passing through the gamepad axes reported by the browser - and the depthmap_navigation.xml was using them directly for controlling - but in the WebVR API and in the WebXR API that 'axes' were stored differently.

In the WebVR API the controller axes were stored as Array like this:

Source code

1
axes = [X,Y]
where X,Y are the input values, regardless if they were from a touchpad or a thumbstick.

but in WebXR the axes are stored like this:

Source code

1
axes = [X-touchpad,Y-touchpad,X-thumbstick,Y-thumbstick]
That means different values depending if they are from a touchpad or a thumbstick.

In the next release (krpano 1.20.7) the depthmap_navigation.xml will be updated for that.

Best regards,
Klaus

spacerywirtualne

Professional

Posts: 984

Location: Poland, Europe

Occupation: krpano developer : virtual tours

  • Send private message

3

Thursday, May 21st 2020, 11:02am

Hi Klaus

In the next version of webvr.js, will it be possible to detect which button was used? From the right controller or left controller...

Piotr
Your own online, cloud tool for creating virtual tours - www.cms4vr.com

facebook page :: youtube

cms4vr team *thumbsup*

4

Thursday, May 21st 2020, 11:51am

In the next version of webvr.js, will it be possible to detect which button was used? From the right controller or left controller...

Hmm... no, why?
That's already possible and I don't know any requests for changing anything related... *confused*

5

Thursday, May 21st 2020, 12:27pm

"In the next release (krpano 1.20.7) the depthmap_navigation.xml will be updated for that."

Can I participate in testing 1.20.7? I have already seen a virtual tour with this version. 2 projects are waiting for changes in VR mode.

spacerywirtualne

Professional

Posts: 984

Location: Poland, Europe

Occupation: krpano developer : virtual tours

  • Send private message

6

Thursday, May 21st 2020, 1:17pm

*huh*
Hmm... no, why?
That's already possible and I don't know any requests for changing anything related...
Dear Klaus, I know that, but as everyone has noticed VR ! = XR ...


anyway... thanks for confirmation.
Your own online, cloud tool for creating virtual tours - www.cms4vr.com

facebook page :: youtube

cms4vr team *thumbsup*