I'd like to set the view direction for a pano depending on which pano the user comes from. For example, if a user is in pano A and clicks to see pano B, they arrive in pano B looking in one direction. But if they are in pano C and click to see pano B they arrive in pano B looking in a different direction.

This sort of thing seems fairly important for creating cross-linked tours. I tried using a variable to set a specific pan parameter in the onclick() part of a hostpost and then using that variable as the first part of the lookto() instructions in an action - but this gives me a black pano. Peeking into the options plugin display shows that lookat is NaN/NaN (not a number)... so I'm obviously messing this up completely! :-)

(I must admit that I'm guessing wildly about how to use variables - that's not helping!)

Can anyone offer any advice?

Keith

Sounds brilliant, and SO much simpler than the process I was trying!
The only problem seems to be... that it doesn't work for me. here's my onclick line:


I simply replaced the NULL with view.lookat(180,-1,80), removed the onstart item that set the initial view, and tried it out. This is what I get:

Any suggestions very gratefully received! This seems like the ideal way forward, I just need to find out why the error happens and kill it off.

(BTW, Klaus? The error message contains a spelling mistake. "attriubate" rather than "attribute". :-)

Using lookat() rather than view.lookat() stops the error from popping up, but I get odd results still.

With MERGE in place the pan setting in the destination comes directly from the previous pano. With it set to NULL instead the pan is always 0, no matter what I put in lookat(). So perhaps all that does is stop the error - but not actually *work*! Hmm...

Keith

Thanks for that! Setting the data directly did the trick. Fantastic stuff! :-)

Still experimenting, but: http://www.panoramaphotographer.com/spaces/westway/

Keith