Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
i know the 'requirements' for mobile devices, but what is, if some devices or browser still does not work.Example: so on a Motorola Moto X™ (2. Generation) with Chrome 49.0.2623.91 it doesnt work, but the same device with firefox 45.0 can change viewer to VR.
First it would be necessary to know what doesn't work - e.g.but what is, if some devices or browser still does not work.
thnak you klaus for your answer.First it would be necessary to know what doesn't work - e.g.
Okay, sorry for my confusing posts. I want the WebVR Plugin running stable on most devices.Sorry, but you still didn't say WHAT isn't working - the VR support detection or the gyro?
And if it's the VR support detection - is WebGL available at that time? (check by the info in the contextmenu or the krpano log)
And is the gyro plugin available? (check if the gyro icon of the vtour skin is there)
You can adjust it anytime for your needs - look in the vtourskin.xml at the 'skin_deeplinking_update_url' <action>.The new deeplinking option in the vtourskin is very useful for me, but should have 2 modifications.
Could somebody confirm if it is a bug? @Muxi had the same problem and trying to create a very simple XML and running the loadscene method also produces the same effect: The previews view is shown again before loading the new one. This is specially confusing in the case of ZOOMBLEND (old image shown zoomed when it shouldn't)We have updated krpano from 1.18.5 to 1.19 and we have one issue: When loading a new scene ( krpano.call("loadscene(scene" + fileName + ", null, null, null);");), the previous image is now shown for a while before loading the new image and this is really causing some confusion in the navigation. You can check what I exactly say if you go to https://goo.gl/dG9UAq and try to navigate using the hotspots. It used to work fine with 1.18.5. Any ideas?
I thought 1.19.pre3 and 1.18.5 are the latest releases available up to now. And I also though in general wmode only applies to flash, although it look like it does apply to HTML5 in the case of "transparent".I'm not sure what you mean, but maybe re-test that with the next release. A lot of things have already changed since the pre-release-3 - e.g. the whole wmode=transparent support (used in your example) wasn't finished in that pre-release.Could somebody confirm if it is a bug?
Best regards,
Klaus
Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »WilcoVDS« (25. März 2016, 11:59) aus folgendem Grund: Screen jitter on android fixed, seems we were using gyro.js instead of gyro2.js, silly mistake.
Benutzerinformationen überspringen
Wohnort: Netherlands
Beruf: Krpano custom coding / Virtual Tours / Photography / Musician / Recording engineer
: https://pame.virtualtuur.com|
|
Quellcode |
1 |
<action name="openAd1"> webvr.exitVR(); openurl('http://vermontpeaks.com',_blank);</action>
|
I tried that first, unfortunately there is something that prevents the openurl() call to execute when done from within VR mode. On closer inspection, I believe what is happening is that openurl() is causing the popup blocker in Chrome and Safari to trigger. While I know I can white list this, my viewers won't know that. Anyone eles have a problem with openurl() triger popup blocker?
Zitat
"maibe just try no to exit VR and just open the url, it should exit anyway, or try first open url and then exit"