Sie sind nicht angemeldet.

panomexico

Anfänger

Beiträge: 17

Wohnort: Deutschland / Mexiko

  • Nachricht senden

61

Sonntag, 10. Juni 2018, 21:16

Hallo Klaus,

vielen Dank für die 3D TV Unterstützung, diese habe ich heute mal mit meinem 55 Zoll Samsung TV und einer aktiven Shutterbrille mal getestet, perfekt!

Leider stürzt mein iPad und iPhone im VR Modus ab, Dein Beispiel mit dem Rohbauhaus klappt allerdings.

https://3d.web-design-opelt.de/examples/stereoscopic_tulum/

<krpano onstart="loadscene(stereopano6);">

<scene name="stereopano6">

<!-- startup view -->

<view hlookat="140" vlookat="0.000" fovtype="MFOV" fov="120.000" maxpixelzoom="1.0" fovmin="70" fovmax="140" limitview="auto" />

<preview url="panos/pano6_mono/preview.jpg" />

<image stereo="true" stereolabels="l|r" prealign="0|220|0">
<cube url="panos/pano6_stereo_%t/pano_%s.jpg" />
</image>


<hotspot name="spot1"
url="spot_curvedarrow.png"
ath="130" atv="9"
distorted="true"
edge="bottom"
depth="700" scale="0.5"
flying="0.05"
onover="tween(scale,0.55,easeOutExpo,0.2);"
onout="tween(scale,0.5,easeOutExpo,0.2);"
onclick="tween(alpha,0,0.2,default,WAIT); loadscene(stereopano3,null,MERGE|KEEPMOVING,COLORBLEND(1.0,0x000000,easeOutSine));"
/>


</scene>


<scene name="stereopano3">


<preview url="panos/pano3_mono/preview.jpg" />

<image stereo="true" stereolabels="l|r" prealign="0|25|0">
<cube url="panos/pano3_stereo_%t/pano_%s.jpg" />
</image>

<hotspot name="spot2"
url="spot_curvedarrow.png"
ath="115" atv="9"
distorted="true"
edge="bottom"
depth="700" scale="0.5"
flying="0.05"
onover="tween(scale,0.55,easeOutExpo,0.2);"
onout="tween(scale,0.5,easeOutExpo,0.2);"
onclick="tween(alpha,0,0.2,default,WAIT); loadscene(stereopano6,null,MERGE|KEEPMOVING,COLORBLEND(1.0,0x000000,easeOutSine));"
/>


<hotspot name="spot3"
url="spot_curvedarrow.png"
ath="-75" atv="9"
distorted="true"
edge="bottom"
depth="700" scale="0.5"
flying="0.05"
onover="tween(scale,0.55,easeOutExpo,0.2);"
onout="tween(scale,0.5,easeOutExpo,0.2);"
onclick="tween(alpha,0,0.2,default,WAIT); loadscene(stereopano2,null,MERGE|KEEPMOVING,COLORBLEND(1.0,0x000000,easeOutSine));"
/>


</scene>

Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »panomexico« (10. Juni 2018, 21:33)


62

Donnerstag, 14. Juni 2018, 19:07

Hi,

Leider stürzt mein iPad und iPhone im VR Modus ab, Dein Beispiel mit dem Rohbauhaus klappt allerdings.
https://3d.web-design-opelt.de/examples/stereoscopic_tulum/

Das 'Abstürzen' auf iOS ist kein Wunder ;-) - die Würfelbilder sind 3759x3759px groß - und das ist für die meisten iOS Geräte einfach viel zu viel, aber auch für viele Android und Desktop Geräte grenzwertig.

Ich würde hier entweder Multiresolution-Panoramen oder zusätzliche kleine Bilder für Mobil Geräte empfehlen.

Schöne Grüße,
Klaus

63

Freitag, 15. Juni 2018, 10:09

Hello Klaus,

it seems some Android 8.x-devices have some problems with the gyroscope support of krpano (even with the sample website of the WebVR-version) - using just the gyroscope button or the VR mode. The devices are only able to look up and down but not left to right. We've tested it with multiple devices, the majority is working just fine. Others are not (namely the Sony Xperia/Compact range of devices). We are using the latest Chrome version on all devices 67.0.3396.87. Any ideas? Might this be a limited support by the device? Anything we could try?

64

Freitag, 15. Juni 2018, 10:25

Hi,

The devices are only able to look up and down but not left to right.

That means that devices doesn't have a gyroscope sensor!

The acceleration sensor is used for tracking the up/down rotating and the left/right rolling - it does that by measuring the angles against the earth gravitation.

But for the rotation horizontally around a gyroscope is absolutely necessary.
Additionally the gyroscope is used for the fine/short-time movements as the acceleration sensors are very noise and inaccurate compared to the gyroscope sensors.

Now the main problem - it's currently not possible to detect if the device has a gyroscope sensor or not. That might eventually change with the new Generic Sensor API from Chrome (krpano will support that soon too). Because when it would be detectable that the device doesn't have a gyroscope, it would be possible not showing the gyroscope and vr icons.

Best regards,
Klaus

65

Freitag, 15. Juni 2018, 11:27

Wow - thank you for the precise answer!

66

Samstag, 16. Juni 2018, 19:17

zoomToSpotsExtent() on bingmaps

Hi Klaus,
First of all thank you for the new bingmaps.js (1.19.pr17)!
Please note that the Bing Maps Plugins do not treat correctly the caller.zoomToSpotsExtent(); in the vtourskin.xml.

For test just change the maps_type="google" to maps_type="bing" in the ..\krpano-1.19-pr16-win\viewer\examples\demotour-corfu\tour.xml.
None of the checked bingmap.js (ver 1.19-pr*, 1.18.6/3) does not work for me while the google maps does.

Any idea?
Thank you and have a great day!
Pavel

Please let me share my workaround:
You need to define the location in the vtourskin.xml:

Quellcode

1
    <layer name="skin_map" ... lat="48.48143" lng="18.721371" zoom="8"  ...>

and condition the ZoomToSpotExtend in the vtourskin.xml

Quellcode

1
2
3
<action name="skin_addmapspots" scope="local">
...
if(skin_settings.maps_type == 'google', caller.zoomToSpotsExtent(););


Enjoy,
Pavel

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »pur« (19. Juli 2018, 18:00) aus folgendem Grund: Sharing the workaround


panomexico

Anfänger

Beiträge: 17

Wohnort: Deutschland / Mexiko

  • Nachricht senden

67

Montag, 18. Juni 2018, 15:54

Hi,

Leider stürzt mein iPad und iPhone im VR Modus ab, Dein Beispiel mit dem Rohbauhaus klappt allerdings.
https://3d.web-design-opelt.de/examples/stereoscopic_tulum/

Das 'Abstürzen' auf iOS ist kein Wunder ;-) - die Würfelbilder sind 3759x3759px groß - und das ist für die meisten iOS Geräte einfach viel zu viel, aber auch für viele Android und Desktop Geräte grenzwertig.

Ich würde hier entweder Multiresolution-Panoramen oder zusätzliche kleine Bilder für Mobil Geräte empfehlen.

Schöne Grüße,
Klaus



Hallo Klaus, ok Danke ich werde es ändern

VG Matthias

68

Dienstag, 17. Juli 2018, 15:03

Hi Klaus

I have a Problem with the new Editor. With my custom skin I do get the Error: "Not a krpano MAKE VTOUR tour.xml file! No editing function available..."
It must be checking something in the custom vtourskin.xml as i changed to standard tour.xml file an error was still there.

What do i need to check in my code to get the Editor running`?

Thanks
Sven

69

Mittwoch, 18. Juli 2018, 20:24

Hi,
I have a Problem with the new Editor. With my custom skin I do get the Error: "Not a krpano MAKE VTOUR tour.xml file! No editing function available..."
It must be checking something in the custom vtourskin.xml as i changed to standard tour.xml file an error was still there.

What do i need to check in my code to get the Editor running`?

The tour.xml need to contain the text 'vtourskin.xml' because the editor is only designed to edit default tours.

Best regards,
Klaus

70

Gestern, 22:57

upgrade from old version

If I have multiple VT and panos with version 1.17 and now I will use 1.19 is possible to upgrade them or I have to create them again?