Posts by Alain


    Problem 1
    In VR-Mode with a Cardboard V2 and a contemporary Android smartphone we see the cross double.
    After manually adjusting the screensize, the problem is solved.
    But on a iPhone it works without manually adjusting.
    In older version, maybe one or two years ago, we didn't have that problem.
    And we think, we cannot expect from our customers, that they manually have to adjust their devices.

    Problem 2
    While watching the panorama it wobbles, like a wave is going through the image.
    Has it to do with the lenses of the Cardboard headset? How can we fix this?

    webvr.js v.1.20.11 is installed.


    Kind regards

    I added that tag in the tour.xml File after the skin_settings.
    But it did not solve the problem.

    Any news or hints about this?
    A customer of us is complaining about non working vr-mode on iPhone and Android Device.

    24.06.21 Edit:
    Android Devices work.
    But iPhone 8 Plus, Version 14.5.1, Safari does not.

    And here is the Scene to test:…oniswil-update/

    Kind regards


    We have a tour made in krpano 1.19.
    Gyro worked on Safari iOS12, but now on iOS14 it does not work anymore.

    I tried to update the tour to krpano 1.20.8
    I just copied all files from to plugin-folder to the plugin-folder of the existing tour (overriting existing files).
    But it did not help, gyro still does not work.

    What do I do wrong?

    Kind regards

    That different 3d-softwares use different orientations and scales of their coordinatsystem is clear to me.

    But I do not understand why the center-attribute of a depthmodell has a differnt x,y,z-orientation than hotspots do.
    Should it not be equal?

    Does krpano have one fixed camerastandpoint? And when moving in 3d-space, then just the depthmodell (or the cube if you have no depthmodel) but not the camera itself moves, right?
    If yes, is the panorama-image always projected from that fixed camera to the current position of the depthmodel?

    Do values in the center-attribute of the depthmodel-element define the offset to the origin of the depthmodel?

    Thanks for that overview, I missed something like that *smile*

    Kind regards

    Hi Mischa
    Thank for that clarification!
    Good to know that I'm not the only one that stumbles over this orientation obstacle course *smile*

    I came approximatly to the same conclusion as you did:

    Maybe Klaus can help us and explain why we have to change the orientation (and scale) of the coordinate-system from 3d-software to krpano-hotspots to krpano-depthmodel. I feel like doing a mental double backflip with screw *wacko* If there would be any kind of understandable logic behind it, everything would be easier to implement *smile*

    Kimd regards

    To clarify the question:
    Why is the orientation of the Blenderscene not the same as the orientation of the image and the image not the same as the orientation of the depthmap? Why has each its own orientation in 3D space?
    From my point of view all elements in 3D space should have the same orientation.
    Am I wrong?

    Kind regards


    I can't follow krpano's logic of defining coordinates in 3d space.

    I did build a tour of 4 standpoints in a Blender. Each cameraposition is on a grid of 300 units.
    I analysed the "tempel of abu simbel" example to see how to position hotspots, panorama-image and the center attribute of the depthmap-element.

    I came to a coordinates-converting conclusion like this:
    The screenshot is from Blender.

    The gray squares visualize the hotspots on the floor (HS1 to HS4).
    The orange geometry represents the depthmap-model.
    The black cube (I asume) represents the cube of the pano image.

    Blender, scene.image and scene.image.depthmap seem to use its own orientationlogic.

    Does anybody know how the logic behind the diffent orientations is?

    Kind regards

    I found the solution.

    /*copy the center-attribute-value to every scene.image.depthmap*/
     for(set(i,0), i LT scene.count, inc(i),
     copy(sc, scene[get(i)]);
     txtsplit(get(camera_coordinates[get(i)].value),',', coordinates_per_camera);
     set(centerdata, calc(coordinates_per_camera[2].value*-1 + ',' + coordinates_per_camera[1].value + ',' + coordinates_per_camera[0].value));
     copy(, centerdata);
     trace('depthmap center:',;
     trace('scene 0:', scene[1];

    A scene-element looks like this:

    The value of the center-attribut in the depthmap-element looks correct when I trace it.
    But when I click to the next scene the depthmap-position is not correct (but also here, tracing the caller.linkedscene-object after the click, outputs the correct value).
    Only when I hardcode the center-attribute-value then the depthmap-position is correct.

    Any idea what I do wrong?

    I try to modify the attribute of depthmap-elements.
    To get all style-elements I can loop through them by doing something like this:

    for(set(i,0), i LT style.count, inc(i),
    style[get(i)].atribute = value;	

    But for depthmap-elements this does not work.

    How can I manipulate attributes of depthmap-elements?

    Kind regards

    I'm creating a custom droplet.

    Inside the scene-element I need an image-element.
    Something like this:
    <image style="Camera_001">
    <cube url="panos/Camera_001.tiles/%s/l%l/%v/l%l_%s_%v_%h.jpg" multires="512,640,1152,2304" />
    <depthmap style="depthmapsettings" center="300,0,0"/>

    Question 1

    For the style-attribute I added this in the vtour-normal.config:
    # image element parameters

    But this results as:
    <image style="[BASENAME]">
    <cube url="panos/Camera_001.tiles/%s/l%l/%v/l%l_%s_%v_%h.jpg" multires="512,640,1152,2304" />

    I tried with the following variants:

    None of them works. It outputs always the placeholder-name but not the dynamic Basename.
    What do I do wrong there?

    Question 2
    What do I have to do to get a depthmap-element inside the image-element?

    Kind regards

    Hi Calin

    Thanks for your tip.

    If I understand you right, then you would cover every wall, witch has hotspots behind it, with another hotspot?
    That means alot of manual work if you have many rooms *mellow*

    Is there no way to use the Depthmodel to prevent clickable hotspots behind walls?

    Edit 1:
    One other problem occured:
    When the mousepointer is over a hotspot then draging for looking around is not possible anymore.
    Is there a way to keep the dragingevent when the mousepointer is over a hotspot?
    Edit 2: Got it: capture="false" does the trick *smile*

    Kind regards

    Hi Jordi

    Great Plugin!

    We just need a standalone version of that Plugin because we do "synthetic panoramas" aka "renderings" and its mutch easier for us to model the "depthmodel" with our own 3d-software instead of everpano.
    Will you provide it as a standalone Plugin as well?

    Kind regards