Just tried to use this on one pano in a tour of 40 but it does not work. Latest 1.17
limitview="range" hlookatmin="-180" hlookatmax="180" vlookatmin="90" vlookatmax="-100"
Hans
Just tried to use this on one pano in a tour of 40 but it does not work. Latest 1.17
limitview="range" hlookatmin="-180" hlookatmax="180" vlookatmin="90" vlookatmax="-100"
Hans
Also not when you take all the hlookatmin hlookat etc etc away?
So just with limitview..
?
Tuur
Hi,
when using limitview=range and a vlookatmin or vlookatmax value exceeds the nadir(+90) or zenith(-90) edge, then the limiting of the exceed edge will behave the same as in the limitview=lookat mode.
This usage case for this behavior is when e.g. the nadir should not be visible (vlookatmax=60), but at the same time viewing the zenith should be freely possible (vlookmin=-90).
But this not a new behavior, this works already this way since several versions... (I think since 1.0.8.15 or 1.16).
Best regards,
Klaus
Sorry I found out . Must have used the wrong pano to paste from.
As far as I remember it did not work correct unless you added the code to all panos and changed the range to cover full range on those with full 360 range
I can see I have the code on all panos on the old tour.
http://virtualdenmark.dk/dnm/audienssal…rama/index.html
But it seems to work fine now without that.
Or maybe this was only on IOS. Have not checked that yet.
Hans
Don’t have an account yet? Register yourself now and be a part of our community!