That doesn't matter - the url can be defined directly or via style - the result will be the same,Even though the hotspot in VR does not like "url=myinfo.png ", but instead relies on a style being defined..
Benutzerinformationen überspringen
Wohnort: La Paz, Baja California Sur, México
Beruf: KRpano programmer at www.imagen360.com
Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »nautama« (17. Juli 2015, 17:56)
Zitat
<view hlookat="130" vlookat="0" fovtype="MFOV" fov="55" fovmin="45"
fovmax="90" hlookatmax="50" hlookatmin="270" vlookatmax="-55"
vlookatmin="70" limitview="range" />
If I run the same tour Locally on a Mac - latest OS/Window 7 64 bit
using chrome, the view limits go nuts and I get very different results.
If I run the tour from the internet it works as expected in Chrome.
The reason are invalid viewing range limits. The min values should be smaller than the max values!
The reason why it behaves differently in different browser, is that some
browsers need to use Flash locally (e.g. Chrome) and others HTML5 and
the krpano Flash and krpano HTML5 viewer are correctly invalid viewing
limits differently - the Flash viewer corrects only invalid vertical
limits while the HTML5 viewer automatically corrects invalid horizontal
and vertical limits.
I've changed that now for the next release - then the krpano Flash
viewer will also automatically correct invalid (swapped)
hlookatmin/hlookatmax settings.
I'm working on text support for hotspots of course. The problem is when using the real WebVR API only WebGL content is visible, so the textfield hotspots need to be a WebGL texture - but it's not possible to render a HTML content (like text) into a WebGL texture. So a solution a manual html+css parser+canvas renderer need to be used for the text. This is complex and inefficient and can only have limited HTML/CSS of course.I would like to know if the final release of Krpano 1.19 will allow the use of textfield hotspots and/or textfield layers in VR mode. They would be really useful to let the user know where is he heading before going into a new scene through a hotspot. An example of this happens in the Orbulus android app which you can see in this image here: http://bit.ly/1e4WU8L
Do you have a more detailed explanation or a screenshot?The crop on the image of buttons is not made.
With automatically correct I mean that the viewer will check if the min value is larger than the max value and then automatically swap the both.What do you mean by automatically correct ? I've never seen anything about the min s/b less than the max. What would the correct settings be that would give the same left to right, right to left limits?
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
<!-- webvr.xml - WebVR plugin, enter/exit VR buttons, VR cursor, VR setup -->
<include url="%SWFPATH%/plugins/webvr.xml" />
<!-- enable the FAKE VR support to allow testing -->
<plugin name="WebVR" mobilevr_fake_support="true" onentervr="setVRstuff();" onexitvr="resetVRstuff();"/>
<!-- /webvr -->
<!-- VR UI -->
<action name="setVRstuff">
trace('Entering VR mode');
set(hotspot[hotspot1_VR].visible,true);
</action>
<action name="resetVRstuff">
trace('Closing VR mode');
set(hotspot[hotspot1_VR].visible,false);
</action>
|
Benutzerinformationen überspringen
Wohnort: La Paz, Baja California Sur, México
Beruf: KRpano programmer at www.imagen360.com
Zitat
Some mobile devices (e.g. very often the Samsung S5) have uncalibrated gyroscope sensors and this is causing a constant unindented moving called 'drifting'.
The WebVR plugin and also the webvr.xml are offering now a possibility to calibrate the gyroscope sensor to avoid that drifting.
The calibration itself would need to be done only once and will be stored together with the other VR headset settings in a cross-domain HTML5-localstorage.
That's basically fully custom - you can use the onentervr event to show your custom VR UI and the onexitvr event to hide it again.So, is there a way to activate globally a desktop UI only, then the vr UI only, etc ?
We have webvr_hide_all_non_vr_layers in webvr.xml
Should we write our owns webvr_hide_all_vr_layers ?
How do you handle management of both UI, only one at same time depending on vr mode or not ?
That's nothing 'new' that happens 'now'. Some devices just have broken/uncalibrated gyroscope sensors that are slowly drifting. In normal gyro usage that's not that noticeable but in VR mode where everything is magnified even more.regarding this drifting phenomenon, I would like to point out that before getting into the VR world I have never had this problem with the gyroscope plugin in any tour in the devices I have used (iPhone 4s, Galaxy S4, ipod 4 and ipad 3), so why is it happening now?
The gyroscope calibration parameters were saved of course!ther parameters like device and screen size are being correctly saved but not gyroscope calibration
Benutzerinformationen überspringen
Wohnort: La Paz, Baja California Sur, México
Beruf: KRpano programmer at www.imagen360.com
|
|
Quellcode |
1 2 3 4 5 |
<style name="vr_menu_style" depth="800" scale="0.2" distorted="true" ath="0" atv="75" alpha="0.25" visible="false" /> <hotspot name="vr_menu_bg" style="vr_menu_style" keep="true" zorder="5" url="black.png" width="600" height="120" onover="vr_menu_over();" onout="vr_menu_out();" handcursor="false" /> <hotspot name="vr_menu_home" style="vr_menu_style" keep="true" zorder="6" url="texts.png" crop="0|95|280|100" onover="vr_menu_over(); delayedcall(0,tween(alpha,0.75,0.1));" onout="vr_menu_out();" startupxml="" onloaded="copy(startupxml, xml.url);" vr_timeout="1000" onclick="vr_menu_loadhome();" /> <hotspot name="vr_menu_l" style="vr_menu_style" keep="true" zorder="6" url="texts.png" crop="302|92|100|100" ox="-48" onover="vr_menu_over(); delayedcall(0,tween(alpha,0.75,0.1));" onout="vr_menu_out();" vr_timeout="700" onclick="nextscene_loop(-1);" /> <hotspot name="vr_menu_r" style="vr_menu_style" keep="true" zorder="6" url="texts.png" crop="392|92|100|100" ox="+48" onover="vr_menu_over(); delayedcall(0,tween(alpha,0.75,0.1));" onout="vr_menu_out();" vr_timeout="700" onclick="nextscene_loop(+1);" /> |
Dieser Beitrag wurde bereits 9 mal editiert, zuletzt von »suppenhuhn« (30. Juli 2015, 11:23)
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »torentvr« (1. August 2015, 22:49)
Have a look here : http://webvr.info/Hola Todos!
Today I found out that the latest Chromium build is not compatible with VR tours, as previous versions.
Does anyone know if there is a list of the currently compatible browser to show panoramas as VR content?
Thanks in advance