Posts by Joel

    Hi Klaus,


    According to an article discussing iOS 12.2 beta features:

    > Accessing sensor APIs is now disabled by default, so no accelerometer, gyroscope or magnetometer APIs are working unless the user enables a Settings option under “Safari”

    Does this mean Cardboard VR mode won't work anymore in iOS 12.2? *blink*

    I have read through this discussion:…mment-458464696
    Which sounds like they might create a popup asking the user for permissions, but perhaps not in time.

    You have made my day also Klaus!! This was causing a major problem for one of our projects and I was waiting for Google to fix it, but without luck. I have just tested your fix and can confirm this works for Chrome 65.0.3325.109

    It seems I cheered too early *unsure* I thought the jerky effect Aladdin_VR mentioned wasn't too bad, but it turns out it is worse on some devices. I originally tested on a Samsung A5 which was ok, considering the circumstances (a bit jerky, but doable to watch). But on the Samsung S7 and S8 the jerky effect is actually too strong to be able to watch in VR *wacko* This is a major problem for a large project going public next week.

    How can we make pressure at Google for the Chrome update? Are there any channels they are listening to, aside from the bug reports (those I already voted for)??

    Thank you for the updated files Klaus! Handy to have the unit change already prepared/ready for when Chrome 66 comes out.

    You have made my day also Klaus!! This was causing a major problem for one of our projects and I was waiting for Google to fix it, but without luck. I have just tested your fix and can confirm this works for Chrome 65.0.3325.109

    Thank you Klaus for your support and solutions/work-arounds always!

    Thanks for the info and your work Klaus! I can confirm the problem. Tried 3 different Android phones with no problems on Chrome 64 and all three not working on Chrome 65 *cursing*


    A workaround is technically not possible, it's necessary to wait for Google for an update. So please make pressure there.

    I have clicked the star at the bottom of the issue saying "Vote for this issue and get email change notifications". Is there any other way we can make pressure?

    in the code that you have posted above there are no stereo settings...?

    Hi Klaus,

    thank you very much for you reply and help! *smile* You have found the problem for me. Something must have gone wrong when I copied the code into my post, as I did have the 'stereo' and 'stereoformat' options included in my code (hence my reference to the #image.stereoformat page).

    However, I did NOT have a hfov and vfov set (perhaps worth adding this to the #image.stereoformat documentation example ?) and this seems to do the trick! After adding those parameters, the video is shown all around as a sphere instead of as a cylinder. I can imagine that by leaving out hfov and vfov, it either tries to guess the values or use default values or so...? which resulted in a cylinder form apparently.

    Thanks again for the help!


    I'm trying to create a pano tour including a spherical stereoscopic panoramic video (with VR support), but without success.

    The video plays just fine, but is shown as a cylinder form and not as sphere. Which means I get a black round area at the top and the bottom (basically looking like a ceiling and a floor when you are in VR), rather than seeing the video all around like the non-stereoscopic version.
    - whether I change the panorama type to 'sphere' or 'cylinder' doesn't make a difference.
    - also changing the stereoformat to SBS and using a side-by-side video doesn't make a difference.

    As a test, I have used the 'demotour-stereoscopic' example, from the examples in the krpano software download, as a basis and have added a video using the instructions/code from as followed:

    <plugin name="video"
        <sphere url="plugin:video" />

    Can anyone tell me what I am doing wrong, or does anyone have an example of a spherical stereoscopic panoramic video anywhere? I haven't been able to find a working stereoscopic example, only for images but not video.



    I've been struggling and testing for hours and can't find how the relation between pixel size/distance and krpano ath value works *confused* *cry*.

    I have a pano image of 7882px * 3941px. Let's say I have an image of 100px * 100px positioned at ath=20 atv=0 and I want a second image of 100px * 100px EXACTLY 100px to the right of it (so stuck to it, no overlap, no gap in between). How do I calculate the ath of the 2nd hotspot image?

    I need a formula for it, because the hotspot size will be different every time (e.g. 130px, 246px, etc) and not always 100px.

    I thought I could calculate the ath from pixel value as followed:

    ath = (x / imagewidth - 0.5) * 360

    but somehow with 100 and 7882 this gives me 4.567369 (the middle example in screenshot attached), which is way too little. I noticed it was 4/10 of what it should be (but I have no clue why!), so multiplied it by 2.5 (or 4/10) to get the example on the right, which fits seamlessly and is what I want to achieve. But when the hotspot size changes, to 200px for instance (example on the left), this value doesn't work anymore and there is a gap.

    Anybody knows how I can get the ath position/difference if I know the pixel position/difference?