Jumping to locations within large project

[Jackson]

I have successfully installed a Pano2VR project onto an Oculus Go using VR Tourviewer and am genuinely impressed with the results 

However, the project is rather large and I would really like to offer the ability to jump to a number of key locations (from anywhere in the project).

Is there a way to add (and name) certain predetermined nodes to the contextual menu which the user can bring up?

At the moment, the user might have to navigate 10-12 times (each with a loading screen delay) in order to access key locations within the project, with is rather frustrating.

[Ruud van Reenen]

Hi Jackson!

Yes, you can add items to the 'context menu' (which can be opened with a triple click on the background, or use 'Back button: show dialog' to use the back button) by adding a hotspot with the text '_hidden' in the hotspot ID, for example 'Point01_hidden'. Then it will be added to the menu but won't be visible in the panorama.

If you add these hotspots to the Pano2VR Master Node, these hotspots will be added to all panoramas. Note that the items in the menu will be sorted by hotspot title, so use numbers in the title if you want them to appear in a specific order.

Alternatively you can use '_nomenu' in the hotspot ID for hotspots that show up in the panorama but that you don't want to see in the menu.

Apparently the Knowledge Base article about this is missing, it will be added again soon.

[Jackson]

Sounds great Ruud! Thanks very much for this swift and helpful reply.

Just a couple of (hopefully) quick follow-up questions:

I don't want any of the other hotspots to be displayed in the menu. Can I hide all of them without having to manually add  '_nomenu' to each one?

If I add the '_hidden' hotspots to the master node in Pano2VR, will they not be displayed within the output for the web? (I'm currently using a single Pano2VR project with two separate outputs: 1 multi-resolution version for the web and 1 single resolution version for VR Tourviewer. Ideally, I would like to keep this set-up of one single project, rather than creating two separate ones, as I'm very likely to keep adding to the project over the coming months.)

[Ruud van Reenen]

You can't hide all standard hotspots from the popup menu globally at the moment, but I'll consider adding an option for this in the next update.

If you don't want the '_hidden' hotspots to appear in the Web version, you could probably use a skin-ID that has no definition in the skin. I think that will hide them from view. For example: ht_hidden