• Hi,

    the problem seems to be the z/deep-ordering of the hotspots...

    In the current xml code, the name of the cube/images will be used as zordering, but for some strange reason the faces were sorted in the wrong order...

    As workaround, use a code where the zorder will be directly specified as number,
    e.g. here the changed actions - changed code in red:
    <action name="addface">
    addhotspot(%1);
    set(hotspot[%1].url, %2);
    set(hotspot[%1].ath, %3);
    set(hotspot[%1].atv, %4);
    set(hotspot[%1].width, 1000);
    set(hotspot[%1].height, 1000);
    set(hotspot[%1].distorted, true);
    set(hotspot[%1].enabled, false);
    set(hotspot[%1].visible, true);
    set(hotspot[%1].alpha, 0.0);
    set(hotspot[%1].details, 16);
    set(hotspot[%1].zorder, %5);
    </action>

    <action name="addcube">
    addface(face_%1_F, %1_f.jpg, 0, 0, %2);
    addface(face_%1_L, %1_l.jpg, -90, 0, %2);
    addface(face_%1_R, %1_r.jpg, +90, 0, %2);
    addface(face_%1_B, %1_b.jpg, +180, 0, %2);
    addface(face_%1_Z, %1_u.jpg, 0, -90, %2);
    addface(face_%1_N, %1_d.jpg, 0, +90, %2);
    </action>

    ...

    <action name="start">
    addcube(dia,1);
    addcube(noche,2);
    </action>

    Best regards,
    Klaus

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!