Thank you for the info, I really appreciate it. I guess I will have to include a separate "fullscreen" link outside of my iframe that simply loads the dedicated tour page... maybe I can write it such that it only shows on iOS, as to not clutter the rest of the sane world :P

Quoted The iPhone doesn't support the HTML5 fullscreen mode at all. How can Apple be this bad... I have no words to express my feelings of frustration towards things like this... it's completely nonsensical... Is there official Apple documentation that describes this lack of support? Is everything that runs inside iOS affected? or is it per-browser? (e.g. does Chrome for iOS support it?) Thanks for the code to force support... if I were to add this (to tour.xml?) what would happen on an iPhone?...

I do not own an apple device, so I only noticed this problem at a recent convention, when I had someone load a page that contains an iframe embed of one of my virtual tours, using an ipad. This problem is not present on Chrome on Android, but it is present in the DuckDuckGo browser on Android (which I'm currently using for testing). I recently solved a similar problem that WAS present on Chrome on Android... there was an update to chromium that blocked mobile sensor access, resulting in the remo...

I have also found mobile VR to be quite laggy/jerky. I may be remembering wrong, but when I first started experimenting with krpano about 2 years ago, it was better... have there been browser updates that put more load on a phone when it's trying to track motion?

Quoted from "dan_R" sorry that i revive this old thread, but since i want to do exactly the same i thought to ask my question here. i want to link the plugins folder to a specific path on our webserver. I tried to change every "%SWFPATH%/plugins/swffile.swf" to "https://www.website.com/code/plugins/swffile.swf" whitout luck. Now i want to change the %SWFPATH% path globally, but i don`t know how to do that with the embedpano line. Here is an example from one of my tour.html files. Note that my f...

Quoted from "lerayfle" First, skins and plugins locations are usually %SWFPATH%/plugins and %SWFPATH%/skin, most of the time hardcoded in vtourskin or plugins themselves. If you want to change locations: - either you change %SWFPATH% globally (through the embedpano line in js) - either you ctrl+f the whole code, and override all attributes where you can see %SWFPATH% and change it to your needs, but it will be a lot of work, and it may break on future krpano updates. If you still want to do it,...

I found a solution by posting to a chromium google group and receiving a reply. The thread is here: https://groups.google.com/a/chromium.org…dev/5yqfAXibz1I The short answer was that I now have to explicitly allow some things within my iframes. Source code 1 allow="gyroscope; vr"

I'm having a similar issue which is very problematic for my use-case... I create virtual tours of tiny homes for builders/designers to embed directly on their websites. I just noticed that the embed is not showing the VR option on mobile browsers (which is a feature that I promise to clients). Both my site and the client's site are secure HTTPS, but I guess this update to chromium does not treat the embed as secure? Here is the actual tour location -> https://www.tinynestproject.com/explore/…ome...

Thanks for the reply :) I finally got it working the way I want. But even with your feedback, I struggled to get this working, so I thought I'd share a few things that I learned along the way: My syntax for the path to my custom skin xmls was correct from the start. I was getting errors because I had made modifications to the base vtourskin.xml file (to hide some UI elements), and since that file references all the image files (pngs for the buttons etc.) it was looking for them in the same direc...

Hi, this is my first post and I wasn't entirely sure what sub-forum would be best, so I am posting this here and maybe it can be moved if needed? Last night it came to my attention that VR for my virtual tours was broken. I searched the forum and found the solution, which was that an update to some math in Chrome (degrees vs radians) had caused it, and that I just needed to update my plugin, js, and swf files (I was on pr12, so updated to pr16). In doing so, I found it very cumbersome to replace...