Zitat von »Leon«

DeviceOrientationEvent.requestPermission()
.then(function() {
console.log('DeviceOrientationEvent, DeviceMotionEvent enabled');
})

It seems permission have to be requested separately for DeviceOrientationEvent and DeviceMotionEvent

Hi,

make sure to use krpano 1.20 and also the newer gyro2.js and webvr.js plugin from there!

They already support requestPermission for DeviceMotionEvent (which is used by default) and also for DeviceOrientationEvent.

Best regards,
Klaus

Zitat von »klaus.krpano«

Hi,

make sure to use krpano 1.20 and also the newer gyro2.js and webvr.js plugin from there!

They already support requestPermission for DeviceMotionEvent (which is used by default) and also for DeviceOrientationEvent.

Best regards,
Klaus

Hi, I've updated my krpano to 1.20.2 and copied gyro2 and webvr files but I still can't get my gyro and vr to work on iPhone.


Any idea what to do?

Will this code work even though the motion and orientation option is missing from Safari with the iOS 13 update?

And when I open the gyro2 in 1.20 - its a lot of code..where does the above code go??

I see code examples but no where are tutorials on WHERE to put the code. I know this is a great software, but for experienced code gurus newbies must own way but I'm under deadline, totally lost and ready to find another application. Wont spend the money on a 3rd upgrade if its so difficult to use.

Hi,

please ignore that code above, that's misleading and not krpano related.

All you would need todo is to use the latest krpano version and HTTPS and gyro/webvr will work.

Best regards,
Klaus

Zitat von »klaus.krpano«

Hi,

please ignore that code above, that's misleading and not krpano related.

All you would need todo is to use the latest krpano version and HTTPS and gyro/webvr will work.

Best regards,
Klaus

I've done that, not sure what could be wrong. You can check it out here: https://cityguide360.ba

Hello All,

Reporting about gyro issue - just been updated to 13.1.3 and gyro stop working (1.20.2/https/etc) as there is no motion&orientation permission dialog request. At the same time when I enters WebVR, the motion&orientation request dialog appears fine and it works once allowed.

Also, when using videoplayer.xml from 1.19.pr16 no user interaction is needed when video is muted, while with 1.20.2 it is needed in any case (13.1.3 Safari) - keep using old videoplayer.xml with 1.20.2 as of now and it's just fine.

regards,
Granton

Hello All,

Found the solution - set(plugin[gyro].enabled, true); is a must (even it was enabled before) with onclick event

regards,
Granton

If I may piggyback on this topic.

I have an app that uses a WKWebView to display the panorama. If I open the Panorama on my iOS 13.2.2 device in mobile Safari, the gyro works just as expected (after tapping the button to allow the requested DeviceMotion data).

However, if I open the same URL in my WKWebView inside my own app, the gyro isn't available.

I've tried everything from proper SSL certificates to location permissions on the main app itself, I just can't get the gyro to even be available when used within the app. Again, with Safari everything works, so I think it's fair to exclude SSL etc. as issues.

The DeviceMotionEvent.requestPermission() event returns that permissions have been granted.

Any ideas? We have the PRO version (1.20.2) and our interactive is down because of this issue.

Thanks,

Peter

Can anyone confirm that this fix requires a button click or user interaction to trigger the request permission dialog?

We've got a few projects that are running on an iPad specifically for the gyro control so I was enabling it automatically at startup. I'm now attempting to trigger the permission dialog at startup and I can't seem to get it to fire without linking it to a button. Works fine on a button click (yes, https).

Is there an undocumented function call we can make to the new gyro plugin that will request permission?

Thanks,
bhh

Any news on that?

We are also using the pro version in a hybrid app (Ionic framework). The gyroscope is not available in the current iOS version. I found this related WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=203287 and other solutions show the same problem, e.g.: https://github.com/processing/p5.js/issues/4037.

Does anyone have further informations about this issue?