Starting Point

[Elliot]

Hello

I have a question from a new FPP user. I have an SWF file I created with FPP. Upon opening the SWF file the starting point for the pano is 180 degrees offset from what I see as a MOV file.

Is there some kind of instruction I could assign to the XML that will force the movie to start 180 degree offset.

Thanks
Elliot

[phberlin]

Hi Elliot,

see the FPP documentation that came with your package: It can be done with "panHome" (and tiltHome, zoomHome...)

Regards, Ph.

[Elliot]

Ph

Is the documentation you are referring to, a file called Tutorial.htm

I have looked in that file for "panHome" and I can not find it.

I am sure it is my old age.... :):)

Thanks
Elliot

[Elliot]

Ph

Problem solved, thanks for your recommendation.

Regards
Elliot

[phberlin]

Glad I could help.

Just in case someone else runs across it: The file is called "/tutorials/__index.html", and there's a special section about parameters whose name is -- surprise! -- "Using parameters". The other important chapter is "Hotspots plugin".

Regards, Philipp

[marczr]

I'm still fumbling around in the dark with this one !
I have made my first attempt at a FPP page with an 8 node tour. I'm happy with the start point of some of the panoramas but would like to adjust the starting point for others.
Is this possible using the panoHome param? if so where does this get placed so that it only applies to the specific panos that need adjusting?

Here's my page:
www.threesixtyvr.co.uk/tours/Watcombe/Watcombe.html

TIA
Marcus

PS
I'm also struggling to understand how to place hotspots into the individual panos. I think I could manage it if each node was a separate html+xml pair, but using the loadPano param to navigate I can't work out how to place the navigational hotspots into each pano.

[LepLep]

is there a single person here that studied tutorial?
ALL parameters are there

i also struggled a LOT at beginning with FPP, but it was worth this effort

in tutorial
take a look at panHome tiltHome
take a look also at linked / unlinked parameter to show spots on selected panos

[marczr]

Thanks for pointing me in the right direction LepLep, I'm sure all the info is there somewhere.

I do find [from a newbie with very little coding experience] that the documentation is a little difficult to follow. All the parameters are described but there are very few examples of how they should be compiled and used together. And the navigation is a bit tricky to, I find myself getting a headache pretty quickly when scrolling around the docs looking for the relevant info.

[Elliot]

Marcus

That is a nice panorama. It is a nice house with beautiful gardens. The panorama rotates in a very nice manner either on the small scale or big scale.

Very nice implementation of the drop down menu plugging. It works very good.

I am 57 years old and somewhat technical but all this programing is new to me. Reading the documentation takes a while but it eventually it starts making sense. Additionally, some of the forum members have kindly pointed out in the right direction to few questions I have asked on the internet. Without them I would have not got there on my own.

We have PurePlayer, KRPano, FPP, Pano2VR and each one of them has their own intricacies. FPP may have the best documentation and the best forum.

Please post your questions, I may not know (I am a beginner) but I will try. At least if not able to respond to you I will learn from the other people responding to you.

Regards
Elliot

[marczr]

Thanks Elliot, and apologies for hijacking your thread!

I've re-optimized the images [they were 2048px cubes, now 1300px] to reduce load times, I think they are just about acceptable for FS still.

And I've managed to work out how to set the entry point using panHome in the loadPano param.

But this is an example of what I was saying about the documentation being a bit basic and not having examples.

Here's the original loadPano line for the first image:
The Lawn | loadPano(?panoName=images/Watcombe_1,300,fade);

I knew I had to use panHome=n to adjust the start point, but it was only by trial and error [and seeing some code in another posts' answer] that I found the correct syntax and placement:
The Lawn | loadPano(?panoName=images/Watcombe_1&panHome=90,300,fade);


Still I'm happier now:rolleyes:
I'm off to the beach for a week, so I'll tackle the whole hotspot navigation thing when I get back!

And if you see this Hans, big thanks for pointing me in the direction of Zyphyrs combobox controller, I wasn't even aware of the existence of the flashpanos site!

[Elliot]

Marcus

I am glad you got it to work. Your pano looks great and peaceful. It just gorgeous.

You are right about documentation, all these "kids" that have developed these programs are very intelligent and bright. They forget that some of the users are OLD people like me (57 years). We grew up during the analog days, Morse Code and FAX machines. They have to do these documents for people like me.... :p :p

I took my little boy (11 years) flying a couple of days ago. We tuned to a navigational station and the identifier is on Morse Code. Upon landing I saw him talking with his twin sister and they were laughing... When we got into the car the girl asked me if I learned to fly with the Wright Brothers. My son said, obviously yes. I asked him why thought that I was that old. Well... you can understand Morse code.... Nobody uses Morse code any more....

Can you imagine my children didn't know what a FAX machine was until a few months ago. This is the same issue with these brilliant "kids" that have developed these programs.

Enjoy your weekend at the beach.

Regards (..._._) Over and Out :) :)
Elliot

[cheathamlane]

Hi Elliot:

Ha, I hear you about the Morse Code bit (or is it dit? :p ) -- I worked with someone a while back whose son came in to visit one day. We got to talking about music, and I mentioned my vinyl collection... A little more talking, and the kid asked me if I actually had to flip the record over to play the other side. He had never 'used' an LP -- only CDs.

That said, I don't think the issue you're seeing with the "brilliant kids" is one of them assuming that all people are coders -- I think the issue lies more with the fact that documentation is extremely hard to write (and write well). Even as a fairly good coder (geek) I have issues with the documentation for FPP (and Flex, and Flash, and LiveStage Pro, and...).

Writing in-depth and writing clearly takes time -- and if the forums here, at flashpanos.com, and other places can pick up the slack -- then I am all for the brilliant kid being able to continue coding.

:)

[Elliot]

Patrick

You are correct. I write specifications for new construction, making sure they comply with the National Electric Code... it is a difficult thing..... Specially if I have to write them in Morse code..... Hi hi hi

I learned Morse code when I was about 10 years old. I had a vinyl with a Morse code tutorial. After I learned at 33rpm's I use to run it at 75rpm or whatever the rpm's that was higher. Can you imagine it I learned the Morse code at double the speed I was supposed to learn. When I went to take the test to the FCC I had to ask the examiner to speed up.... Hi hi hi Those were the days when an electronic tube and Morse code where the equivalent of the INTERNET.

Technical writing is very difficult issue... I guess that's why the construction industry use "Blueprints" It easier graphically than in writting... That's why we participate on these forumsto learn from each other....!

I remember when the TV came to our area.... Did you ever had to look at the Indian Pattern on the TV...?

See you :p
Elliot

PD:
When I was young the telephones only came in black and I could recite the car manufacturers with their models..... That is impossible now.... :p

[izoneguy]

Ahhh, the NEC...
I produce training videos for inspectors of
electrical work and the NEC is mentioned about
every 5 minutes!

[Elliot]

Izoneguy

Very interesting.... I also do training on NFPA 99. We interface with NEC when we design the systems.

This very interesting

We should talk later about this
Elliot