An upgrade from x.30 to x.31 is supposed to fix bugs, not to introduce new ones. I was happily upgrading from PTP 2.30 to 2.31 and expected it to be a nobrainer. Not so ! It killed my favourite start for my panos, a zoomout.
I achieved it editing the XML lik this: <autorotate horizon="13.718485" tofov="30.581294" waittime="5" speed="5"/> altered to <autorotate horizon="13.718485" tofov="90.0" waittime="5" speed="5"/>
In 2.31 it doesn't work, for some reason or another. So I have downgraded to 2.30 :-(
arrr... Well the fist one zooms out but the auto rotate does not work too well, it is very gitty and stops and then a bit more then stops again etc..
The second one does not zoom out but the rotate is a little better but still not good.. Perhaps the jpg quality needs to be lower..
I see what you mean about the zoom out.. I guess thats one for Kolor.. I do not think they will be around until Tuesday.. I think Monday is a holiday in France.. but there again, they might take a few days off.. They sure deserve it...
Thanks for the try ! I guess it must be a change in the krpano-version from 2.30 to 2.31, or some issue like that. The XML is identical for the autorotate statement.
I have two parallell installs of PTP 2.30 and 2.31. The two online panos are generated straight forward with each of them and uploaded to two different folders online. They should have behaved in exactly the same way.
Leif
update: in the virtualtour_skin.xml it says <krpano version="1.18"> so it must be something else than a krpano version issue
PTP is set to make jpeg quality = 9, like I've been using for years can't see why this pano should be jittery now
the pano is not interesting in itself, it's just my first non-spherical pano for a long time. and I'm disapointed to see that there is a bug in 2.31 ignoring the tofov="80.0" statement in the XML <autorotate horizon="15.560939" tofov="80.0" waittime="5" speed="5"/>