Have you compared the actions in the

action(show_html_field);">

of each pano?

Maybe something was added or taken away. It seems to be tied to the loading of the html field. At least, that's what I seem to be seeing.

*edit* I assume the action(show_html_field);> is the same on both panos, tied to
<include url="panoraamakuvatfi.xml" />

and probably not the problem.

Maybe something to do with lens flare? That is added in one and not the other.

You may have to post more code from panoraamakuvatfi.xml for a solution.

Jarredja

That is odd.

I only see three differences between the two base xml's
- images - one's jpgs, the others tiffs
- lensflare - one has it, the other doesn't
- lookats - a bit different

None of which I've ever heard causing a problem.

Since both base xml's are calling the exact same extra xml file.

After staring at the non-working pano a bit... I do notice that the sharpness keeps going back and forth... like it's originally at high and then it drops to low... like it would when the autorotate kicks in... but then goes back to high.

Odd.

I closed my other windows where I was looking at the code... It would be good if you could load the non-working base xml file for reference.

Graydon

Hi,

there was a bug with the autorotating and when the "tofov" value was out of the fov limit range (in this example, the high fisheye value and the "limitfov" value are limiting the fov value)

I have fixed it for beta 8,

best regards,
Klaus