shopify analytics ecommerce tracking
VR Tourviewer Forum

Recent Posts

Pages: [1] 2 3 ... 10
An update for Quest is now available!

More info here.
Download it here.

An update is now available for the Quest version of VR Tourviewer.

The following issues are fixed:
fixed: due to an Oculus Quest driver update, the controller could be shown as an Oculus Go Remote, instead of a Touch controller
fixed: orientation issue, the camera could look in the wrong direction when entering a panorama
fixed: improved handling of left and right Oculus Touch controller, use the trigger to switch controlling hand

Hi Ruud,

Dat is geweldig!  ;) That's great, thanks for the superspeedy service!
Support / General Discussion / Re: View orientation not used correctly
« Last post by Ruud van Reenen on August 19, 2019, 22:34:52 »
Thanks again for the example, I've been able to reproduce the issue and it seems the Quest reorients a bit differently compared to the Oculus Go.

I expect to have an update for the Quest version of VR Tourviewer this week which solves this issue.
Support / General Discussion / Re: View orientation not used correctly
« Last post by Ruud van Reenen on August 19, 2019, 16:45:25 »
Hi Thomas,

Thanks for reporting and providing an example.
I'll look into it and if I can reproduce the issue a fix will be available at the end of the week.
Here is a download link for the project:
Support / General Discussion / View orientation not used correctly
« Last post by thomasvandenabeele on August 16, 2019, 11:09:11 »
Hi Ruud and others,

I'm running version 1.1.244, and the view orientations I have set in Pano2VR are not being used correctly:

I have a lounge area in the middle of my project, with a bar on one side, and a restaurant on the other side. In my Pano2VR HTML5 output it works perfectly in the browser:
- When you're going from the restaurant --> lounge --> bar the 'default arrival' view in the lounge shows one side of the room, oriented towards the bar.
- When you're going from the bar --> lounge --> restaurant the 'default arrival' view in the lounge shows the other side of the room, oriented towards the restaurant.

In VR TourViewer this does not work correctly. Each time you enter the lounge area, the default arrival view is the same.

- Is this a known issue?
- Can this be fixed quickly? I would need this to work by end of august. I can copy the same images twice as a workaround, but I'd rather not.


p.s. I can share my project if needed.
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
Support / General Discussion / Re: Jumping to locations within large project
« Last post by Jackson on July 31, 2019, 12:34:13 »
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.)
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.

Pages: [1] 2 3 ... 10