krpano 1.19-pr15 / pr16

panomexico · June 10, 2018 at 9:16 PM

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/

</scene>

</scene>

klaus.krpano · June 14, 2018 at 7:07 PM

Hi,

Quote from panomexico

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

McTristan · June 15, 2018 at 10:09 AM

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?

klaus.krpano · June 15, 2018 at 10:25 AM

Hi,

Quote from McTristan

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

McTristan · June 15, 2018 at 11:27 AM

Wow - thank you for the precise answer!

pur · June 16, 2018 at 7:17 PM

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:

Code

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

and condition the ZoomToSpotExtend in the vtourskin.xml

Code

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

Enjoy,
Pavel

panomexico · June 18, 2018 at 3:54 PM

Quote from klaus.krpano

Hi,

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

sr_raumgleiter · July 17, 2018 at 3:03 PM

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

klaus.krpano · July 18, 2018 at 8:24 PM

Hi,

Quote from sr_raumgleiter

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 needs to contain the text 'vtourskin.xml' because the editor is only designed to edit default tours.

Best regards,
Klaus

jvh · September 21, 2018 at 10:57 PM

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?

klaus.krpano · September 24, 2018 at 5:56 PM

Quote from jvh

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?

Hi,

normally just replacing the viewer and plugin files should be enough.

Best regards,
Klaus

jvh · September 26, 2018 at 4:50 AM

how can update my object tours for just html5 and version 1.19?

Sudarchikov Andrey · October 12, 2018 at 6:48 PM

Quote from klaus.krpano

Here an updated bingmaps.js with that workaround: bingmaps.zip (will be included also in the next krpano release of course).

Hello!
Thank you! it's working now.
Sorry for such late replay.

Andrey

pur · October 29, 2018 at 8:11 PM

Quote from jvh

how can update my object tours for just html5 and version 1.19?

Hi jvh,
Apparently you have older object tours running on Flashplayer krpano viewer. There is no official html5 support for 360 object in krpano 1.19.
Please post the link to your tour(s) to check it out whether my new plugin obj360.xml is able to handle your tour.

Pavel

pur · January 3, 2019 at 11:51 PM

Hi Klaus,
Wishing you and your family a new year of peace and happiness!

Please notice that

Code

loadscene(scene_14, null, MERGE);

is triggering an error:

Code

ERROR: loadscene() - scene "scene_14" not found

when issued in the action with scope=localonly or private:NAME
The scope=local for an action is working OK.

Thanks,
Pavel

klaus.krpano · January 4, 2019 at 5:31 PM

Hi,

Quote from pur

Wishing you and your family a new year of peace and happiness!

Thanks! Best wishes too!

Quote from pur

Please notice that
loadscene(scene_14, null, MERGE);
is triggering an error:
ERROR: loadscene() - scene "scene_14" not found
when issued in the action with scope=localonly or private:NAME
The scope=local for an action is working OK.

Thanks for reporting!
Will be fixed in the next release!

Best regards,
Klaus

pur · January 21, 2019 at 6:11 PM

Hi Klaus,

Is there a way to check out the caller in the jsget() or js()?
The krpano object in the jsget and js is great but passing arguments into it via the global variable is insecure. Especially in deferred actions.
The actioncaller/caller object would be highly appreciated.

Thank you,
Pavel

Blochi · January 23, 2019 at 5:57 AM

Hey Klaus,

speaking of next release ... is it on the horizon? Last one is almost a year old....

is there any chance of lensflares? Been missing them ever since Flash got snubbed out.

klaus.krpano · January 23, 2019 at 9:30 AM

Hi,

Quote from pur

Is there a way to check out the caller in the jsget() or js()?
The krpano object in the jsget and js is great but passing arguments into it via the global variable is insecure. Especially in deferred actions.
The actioncaller/caller object would be highly appreciated.

Good idea, I have added a 'caller' object for the next release now. And the 'krpano' object will be changed from the JS-Interface-Object to the krpano-Interface-Object which additionally also provides direct access to the krpano objects/variables.

Quote from Blochi

speaking of next release ... is it on the horizon? Last one is almost a year old....

Yes.

Best regards,
Klaus

pur · January 24, 2019 at 8:47 PM

Quote from klaus.krpano

Good idea, I have added a 'caller' object for the next release now. And the 'krpano' object will be changed from the JS-Interface-Object to the krpano-Interface-Object which additionally also provides direct access to the krpano objects/variables.

Wow! Thank you, Klaus, for considering it and making it even better!
Looking forward to seeing the new version.
Pavel

krpano 1.19-pr15 / pr16

Participate now!

Users Viewing This Thread