Zitat von »jordi«

I tried with self and top, and it's working , but maibe you don't want to leave the page ...

Yes, I can get it to work with _self and _top, however I need the primary tour window to stay accessible (meaning a new tab or window needs to open -_blank). The thing is that it works with the <layers> onclick attribute but not with a hotspot attribute (see thread from Tuur & Klaus: internetexplorer ). Also some interesting reading / concepts here, but the drawbacks to this approach seam sketchy - http://stackoverflow.com/questions/95146…tdefault-is-set.

anyway I don't think it would be a good idea to jump from VR mode where people wear glasses, to a normal page, it would hurt your eyes...

Zitat

anyway I don't think it would be a good idea to jump from VR mode where people wear glasses, to a normal page, it would hurt your eyes...

Agreed, I'm planning on building a transition page with a countdown that says, "leaving VR Mode in ___ Seconds. Please remove your headset to continue to your selected non-VR content."

Samsung has a special web browser that works within GearVR and they have recently enabled WebVR to work with the GearVR's external sensors, to allow full WebVR experience for Virtual Reality. Official Announcement Just to be clear, Samsung makes two browsers called 'Internet', a regular mobile browser and a special virtual reality browser to use with the GearVR. The GearVR version arrived in December 2015, but did not have the ability to work with any WebVR pages. On an April 1st, 2016 update, they now have experimental WebVR (although it is using a depracated version of WebVR, so most WebVR samples do not work with the browser, but I found a few that do.)

It is first necessary to turn ON the WebVR mode by visiting this link within the GearVR Samsung Internet Browser internet://webvr-enable (be sure to navigate to the URL, it defaults to search)

Now if you visit a site on the normal non-gear-vr Samsung Internet Browser that has a WebVR content, and then you insert the phone into the Gear VR, it will load the same page into the GearVRr Samsung Internet Browser (they are completely different programs and starting the GearVR browser takes a few moments). The page is presented like a movie screen, but if you press 'enter VR' it expands into a full 360 degree experience using the GearVR sensors with html and WebVR content.

Here are the few sample WebVR pages that I found that were still using the old WebVR API and will work with the browser, all are from three.js

cubes
panorama
rollercoaster
video


Unfortunately, the resolution seems to drop significantly, I do not know what size resolution window the browser is reporting, but it is nowhere near satisfactory. I do not know if it is possible to change this setting, it seems to be the only hangup other than some stuttering (javascript frame rate) compared to native VR programs. The external sensors are being used, as well as the low persistence mode, all we need now is the resolution and fix the stutter (which is ridiculous as cardboard Krpano works just fine on mobile so its not that the phone is under-powered) .


Now, how do we get the krpano stereo interface to use the GearVR WebVR API?

Loading a stereo krpano page into the GearVR Samsung Internet Browser is truly horrible currently. It simply does not work well in any capacity (and is not using the WebVR API of the GearVR) It does load and you can enter a stereo 360 mode, but nothing lines up from eye to eye. Perhaps building a special version that uses the deprecated WebVR api found in the GearVR Samsung Internet Browser?

Hopefully someone can wire an example up??? Hopefully in the next version of the browser the newest api is used and higher resolution is made possible. We are at least getting closer!

I have a "simple" question. I`m using krpano 1.19 Pre-release 3 and configured a nice VR tour (http://klanten.invite.nl/viewer/MiPatio/) and its working fine in VR mode. Next tot VR mode i want the hotspots to be clickable in the "normal" mode (drag and drop with your mouse) otherwise the visitor is stuck at the first scene. So my question can i add some code to the hotspots to make it clickable (sort of hyperlink)?


All the scene`s are in 1 tour.xml file.

Code off one off the VR hotspot:


Thnx!

Hello Andre!

Try taking these lines out of the end of http://klanten.invite.nl/viewer/MiPatio/krpano_vr.xml :



Cheers!
Augusto

Zitat von »AndreZ«

I have a "simple" question. I`m using krpano 1.19 Pre-release 3 and configured a nice VR tour (http://klanten.invite.nl/viewer/MiPatio/) and its working fine in VR mode. Next tot VR mode i want the hotspots to be clickable in the "normal" mode (drag and drop with your mouse) otherwise the visitor is stuck at the first scene. So my question can i add some code to the hotspots to make it clickable (sort of hyperlink)?


All the scene`s are in 1 tour.xml file.

Thnx for the solution! The hotspots in the tour are now clickable :) only when i delete those lines there is nothing visible in the intro scene, i have to be in VR mode to see something otherwise the whole page is white and the visitor is stuck. I`ve copied a version to an other location: http://klanten.invite.nl/viewer/temp/

Looks like there's a limitation for clicking hotspots the way you're making it (based on the example from the 1.19 PR 3).
See this post by Klaus on the subject:

Zitat von »klaus.krpano«

Zitat von »Nupsi«

Does the 1.19 use WebGL-Hotspots or still CSS3D?

The pre-releases are using CSS3D by default for normal rendering and WebGL when stereo-rendering.

WebGL support for hotspots could be enabled manually for normal rendering this way:

	Quellcode
1

Note - the hotspot WebGL support is currently not finished in the pre-releases (e.g. clicking the hotspots will be not possible).

But with the final 1.19 release the hotspots will be rendered by WebGL by default.

Best regards,
Klaus

Hi augustommm,
Can you re-post that source code you referenced. Your last reply was missing it.
Thanks,

Here is the link to the post:
krpano 1.19 - Pre Release 3

Zitat von »andrewglover«

Hi augustommm,
Can you re-post that source code you referenced. Your last reply was missing it.
Thanks,

Hmmm thats a shame.. But it will work when i skip the introscene, start directly in the garden? Only when i delete the start hotspot i`m also stuck..

Zitat von »AndreZ«

Hmmm thats a shame.. But it will work when i skip the introscene, start directly in the garden? Only when i delete the start hotspot i`m also stuck..

Check out this tour I'm working on:
http://www.onzeonze.com.br/clientes/cons…ostra/tour.html


I made it based on the droplet one, but the panorama menu is based on the example that comes with the 1.19 PR 3 files.
No introscene, but I think it could be done.
I made some distorted hotspots visible only on VR mode.
You can see my tour.xml here:
http://www.onzeonze.com.br/clientes/cons…mostra/tour.xml


Made some changes to the skin XML file, in order to control webvr plugin via tour.xml.


Hope it's useful

Zitat von »klaus.krpano«

Hi,

use the new krpano release - there the WebGL hotspots are fully supported:
krpano 1.19-pr4

Best regards,
Klaus

Great News!