shopify analytics ecommerce tracking
VR Tourviewer Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Ruud van Reenen

Pages: 1 ... 4 5 [6] 7 8
Support / General Discussion / How to use VR Tourviewer
« on: March 19, 2017, 21:56:40 »
Information about the use of VR Tourviewer can now be found here:

Today a new update of the VR Tourviewer app is released, with some nice feature additions:

0.2 Build 78:
- support for overlay images and video, like in this example:
- support for hotspot popup images, videos and text
- 3D scenery effects: snow, rain and leaves, to use this, add a Userdata tag in Pano2VR: effect=snow / effect=rain / effect=leaves
- use normal webaddress as url instead of path to xml file, the index.html will be scanned for the needed xml file

I've also developed a VR Remote Tourviewer for Windows, to be able to see what a GearVR user is seeing on a laptop or big screen. With normal screencasting applications, a videostream of the screen has to be transmitted. Due to the high CPU/GPU and traffic intensity of this technique, this results in lag in both the VR experience and the casted result. I strongly advise not to use such apps to avoid ruining the VR experience.

With VR Remote Tourviewer this has been solved by running an identical (non-VR) tour on the Windows computer, and only synchronizing the camera movement and user clicks. This results in a very high quality, low latency, synchronized view of the tour on a big screen.

Try the free demo to see for yourself. Check the installation instructions on the download page. The demo is limited to Featured tours only, but a full version can be purchased together with the app soon. If you need it sooner, please contact me.

Announcements / Re: VR Tourviewer 0.2 build 53
« on: February 23, 2017, 12:52:13 »
It seems that's not the right ID.
To be sure: can you try the Device ID app I've added to the dowload section and email me the result?;sa=view;down=10

Announcements / Re: VR Tourviewer 0.2 build 53
« on: February 23, 2017, 10:52:28 »
Ah, my mistake, you need enable USB debugging on your phone first:

- From the Home screen, select “Apps” > “Settings“.
- Scroll down and select “About phone“.
- Scroll down and tap “Build number” seven times until you see a message that says “Developer mode has been enabled“.
- Back out of the screen, and now you’ll have the ability to select “Developer options” in the “Settings” section.
- Under “Developer options“, slide “Developer options” switch to “On“.
- Slide the check the “USB debugging” to “On” and you’re ready to use your device with developer tools.

After that, when connecting with USB and running the adb devices command again it should list your device.

Support / General Discussion / Re: Pano2VR Skin support
« on: February 23, 2017, 09:16:04 »
Pano2VR skins won't be supported literally, but I'm planning to add a set of much used items (different types of hotspots, text/image/video popups) that can be configured/chosen through userdata or tags in Pano2VR or directly in VR Tourviewer with the tour settings button.

If you have requests for specific skin items you'd like to see included, please post them here and they will be considered.

Announcements / Re: VR Tourviewer 0.2 build 53
« on: February 23, 2017, 09:07:12 »
Possibly your (Google) Device ID has changed due to the upgrade. Or you're using another device?
If you can send me the new ID I'll add a signature for that device in the app so you can run it again.

You could try getting the Device ID with:
It seems that this app doesn't work for Nougat though, please let me know if you can confirm this.

The other way to get the Device ID is to use ADB (Android Debugging Bridge) and run the command ‘adb devices’.
The needed SDK Platform Tools (a 4Mb download) can be downloaded here:

Just unzip the package (for example to C:\ADB), it doesn't need to be installed.  Connect your phone with USB.
Then start a command prompt and run: <path to platform-tools folder here >\adb devices
So if you unzipped to C:\ADB then the command will be: C:\ADB\platform-tools\adb devices
You may have to run the command twice. It will then show the device ID for your phone. You can remove the unzipped files/folders after that.

It’s inconvenient that it has to be done like this, but for this stage in development it seems the only way for devices with Nougat. Devices running Android Marshmallow didn’t have this problem up to now.

Announcements / VR Tourviewer 0.2 build 53
« on: February 23, 2017, 00:34:05 »
A new build is released for testing, version 53:;sa=view;down=9


- Added support for Multi Resolution tours!!!

This means that now almost any Pano2VR 360 panorama tour can be watched with VR Tourviewer on GearVR.

Note: the level width is chosen closest to 1536 pixels, but no larger than 2048 pixels to avoid memory problems. If you see a very low resolution panorama, then make sure you output to a level with a width of 1536 in Pano2VR 'Image' settings. Level tilesize ideally is 510 with 1 pixel overlap (= default in 'Advanced').

Please let me know what you think of it!

Best regards, Ruud

Support / General Discussion / Re: How to improve image quality ??
« on: February 22, 2017, 15:34:12 »
The optimal resolution for the GearVR can be calculated:

The S6 and S7 have a resolution of 2560x1440, for one eye that results in 1280x1440 pixels.
The field of view on the Gear VR is approximately 90 degrees on S6 and close to 96 degrees on S7. If a FOV of 90 degrees has 1280 pixels, then 360 degrees has 4 (360/90) * 1280 pixels = 5120 pixels. If you'd use 1440 pixels (if FOV is measured vertically) this would result in 5760 pixels.

Because of the fact that GPU's can handle power of 2 image sizes the easiest, but 2048 would be overkill (memory use for 12 cubefaces with this size) and 1024 would be loss of quality, a size in the middle of 1024 and 2048 has been chosen: 1536x1536. Probably so a single texture of 1536x1536 can be constructed internally from one 1024x1024 image with five 512x512 images. This results in a horizontal size of 4x1536=6144 pixels, nicely above the needed 5760 pixels and without going overboard on pixels/memoryuse.

Support / General Discussion / Re: Hotspots with Ñ , not displaying
« on: February 22, 2017, 10:54:48 »
Fixed in next release. The used font didn't have characters with diacritical marks.
Please let me know if you still miss certain characters.

Support / General Discussion / Re: Hotspots with Ñ , not displaying
« on: February 22, 2017, 09:19:59 »
Thanks for your feedback!

When reproducing this issue the hotspot is displaying but the special character is displayed as a small square instead of the ñ or Ñ. Do you see this too? Can you send me the xml file at ?

I'll look into this and keep you updated.

Support / General Discussion / Re: How to improve image quality ??
« on: February 22, 2017, 09:07:27 »
Thanks for your feedback!

I've looked into it, and it appears that by default the quality settings for GearVR in Unity have been lowered in favor of keeping a high number of frames per second. Because the VR Tourviewer scenes are very low in polygons (but high in texture memory use) I've adjusted the quality settings and it definitely makes a visual difference! Next build with this change will probably be released end of the week.

Announcements / VR Tourviewer 0.2 build 49
« on: February 17, 2017, 19:32:55 »
A brand new release!

For me as developer it's a major milestone, what started as an idea is now really becoming a fully functional application for the Gear VR. With this release the development stage is moving from alpha to beta. A big thank you to everyone who has reported bugs and shared ideas and suggestions, please keep it coming!

With the current addition of the VR keyboard to add your own online tours (finally), the majority of the final (menu) functionality is now present. Development will soon focus on adding more features inside the tours themselves: adding support for links to other tours, polygonal hotspots, image hotspots, video, surround audio.

I hope you like this release, and looking forward to your feedback, ideas and bugreports!;sa=view;down=8


- added: VR keyboard, use the + sign in menu to add your own online tours, added tours are stored in 'Viewed'
- added: functionality to add/remove favorites and viewed tours
- added: show reason when tour from storage is found but can't load

- add more functionality to panoramas: link to other tour, image hotspot, video, surround audio
- add functionality to modify titles/subtitles of favorite and storage tours
- allow more than 9 tours in each menu section, currently no more than 9 can be displayed
- add ability to parse html files to find the the xml file, so easy urls (to index.html files) can be used to add tours
  for example: use instead of

Support / General Discussion / Re: SD card location
« on: February 15, 2017, 10:02:11 »
Thanks for the feedback, good to hear it runs well!

Access to the external SD card is being worked on, it's trickier than I thought. Hope to have the solution this week.

Support / General Discussion / Re: XML settings on Pano2VR
« on: February 12, 2017, 23:22:13 »
The XML file is needed by the app, so it should not be embedded in the HTML file.
The HTML file isn't used at all, only the XML file and the images/hotspots/lensflares mentioned in the XML are loaded.
So 'Embedded XML' should be unchecked.

'Create files for external embedding' can be checked or unchecked. It stores the preview image and location to the preview image for the tour for example. At the moment the files it generates aren't used yet by VR Tourviewer, but support for it is planned.

Make sure for output you have set 'Image' to 'Single Res' (Multi Res isn't supported yet) and Cube Face Size to 1536px for optimal results.

Announcements / VR Tourviewer 0.2 build 46
« on: February 12, 2017, 21:36:34 »
There's a new version available: VR Tourviewer 0.2 Build 46


Beta 0.2 build 46
- app should now be using the right path for external SD card on S7/S7 Edge. Tours can then be stored on the external SD card in: Android/data/com.vrtourviewer.vrtourviewer/files/VRTourviewer
This folder should exist after running build 46 at least once, and should contain the file 'log.txt'. Feel free to use subfolders to organize tours.

Beta 0.2 build 45
- several bugfixes
- better debug messages for storage location determination on S7/S7 Edge
- application errors are collected with Loggly (external logging service) for more efficient bughunting

Pages: 1 ... 4 5 [6] 7 8