Page 1 of 1

Use more than one Tour Node Hotspot in a Node

Posted: Fri Dec 15, 2017 3:51 pm
by DMcNeill
Hi,

Is it possible to have more than one Hotspot Tour Node in a single Panorama?
I want to add a few different icons to the hotspots in a panorama to highlight the different types of areas the user will be going to.

If I add a new hotspot in the Skin Editor it seems to transfer to all of the hotspots in the panorama no matter if it is an information hotspot or Tour Node hotspot. If I click on a hotspot and change the Skin ID to the one I want in the Skin Editor, it does not make any difference.

Re: Use more than one Tour Node Hotspot in a Node

Posted: Sun Dec 17, 2017 4:09 pm
by Hopki
Hi,
Use Skin-ID, you can over type the defaults with are ht_url, ht_image etc.

Example:
Create hotspots in the skin editor and give them say the ID of hs_blue, and hs_green
Then in the hotspot viewer mode add a hotspot and in teh Skin-ID type in ht_blue. This hot spot will use the Blue hotspot template and image.
Then add another hotspot and type in the Skin-ID ht_green. This will use the Green hotspot.
Regards,
Hopki

Re: Use more than one Tour Node Hotspot in a Node

Posted: Mon Dec 18, 2017 8:43 pm
by DMcNeill
Hi,

Thanks for the response. I will give it a go.

Is it important that the hotspot skin has the ID beginning with hs_ ?

Re: Use more than one Tour Node Hotspot in a Node

Posted: Mon Dec 18, 2017 11:14 pm
by 360Texas
Here is a full list of Pano2vr 'Place holders' and their function located in the Documentation.

https://ggnome.com/doc/pano2vr/5/placeholders-list/

Re: Use more than one Tour Node Hotspot in a Node

Posted: Tue Dec 19, 2017 3:23 pm
by Hopki
Hi,
Nope, it can be anything as long as the ID for the Hotspot Template in the skin is the same as the Skin-ID it will work.
Regards,
Hopki

Re: Use more than one Tour Node Hotspot in a Node

Posted: Wed Dec 20, 2017 5:08 pm
by DMcNeill
Thanks for the help.

I tried it again and it worked. I could have sworn I was picking the ID from the Skin Editor from the drop down in the Skin ID field, but it works fine now.

Cheers.