Dear visitor, welcome to krpano.com Forum.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.

New onxmlerror event - it will be called on xml-loading or xml-parsing errors and allows a custom error handling and also to continue using the viewer after errors (only available in the HTML5 viewer).

As alternative to the 'devicemotion' event, the 'deviceorientation' event could be used (here the device drivers are doing the sensor data fusion,
but unfortunately not very good on Android).

And in that 'deviceorientation' event there is the next Chrome bug:
instead of updating the senor data as often as possible (or at least 60 times per second), the updates are done only 5 times per second.
Here that related Chrome bugreport:
https://bugs.chromium.org/p/chromium/issues/detail?id=819413

The workaround is now to use the 'deviceorientation' event instead of the 'devicemotion' event for Android Chrome 65.
Even when it's not as good as it should be, it's better than nothing for the moment.

The next Android Chrome update (to Chrome 66) where this will be fixed is scheduled for April 17th, 2018 (source).

The workaround will be applied automatically by the gyro2.js and webvr.js plugins when the Chrome versions is between
65.0.0 and 65.0.3325, so if Google decides to release a fixed Chrome 65 version in the meantime,
the workaround will get automatically disabled and everything will work as good as possible again.

The updated gyro2.js and webvr.js plugins will automatically check for the Chrome versions to use the right unit for the particular Chrome version.

Add a workaround for the Chrome 63 on Windows 10 'pointerlock' bug that causes jumpy mouse movements in VR.

Add a workaround for the WebVR support for the 'Samsung VR' GearVR browser (report).
Now the 'Oculus Browser' and the 'Samsung VR' GearVR browsers are both working, but the Oculus Browser would be currently the preferred/recommended one - there the WebVR API is enabled by the default, the rendering resolution is higher and the performance better.

Add a workaround for a Mac Safari 11.0 WebGL video-texture browser bug (report).
This is also a core browser bug and the workaround is to render the video first into a canvas before using it as video-texture. This is not very good for performance, but at least it shows the video again.
With the Mac Safari 11.1 version this will be fixed again.

New: combobox.xml plugin - new callonclickafterclose setting to define when the onclick event of the items should be called (this can be necessary to use for browser features that require a direct user-interaction, like entering fullscreen or WebVR mode).

New: Support outputting encrypted files directly to the console by using -out=stdout (request).

Fix: Some offsets of WebGL hotspots with zoom=false and distorted=false were not stage-scaled.

Fix: Wrong position of non-distorted hotspots with depth != 1000 when using fisheye viewing distortion.

Fix: Don't use the 'beforeunload' event for explicitly deleting WebGL resources. It has too many side-effects (caused by browser-bugs). E.g. in Chrome that event will be wrongly sent when opening 'mailto:' links and in Firefox it breaks the page when going back in the browser history.

Fix: Container elements with bgcapture=false were not receiving over/hover/out events when hovering a children layer (report).

Hi, I noted changes in encryption (krpanotools -> Encrypt tool). Now for default is private encrypted? Please comment about to best, secure way for protect / encript...

Private-encryption was always the default, only the UI has changed - previously there was a checkbox for private-encryption and that was checked by default, now there is a checkbox for public-encryption and that is 'unchecked' by default.

About the 'best, secure way': just enable all settings the Protect Tool
But please note - there is no absolute security possible (and can't be) - as this is client-side-only decryption it's only 'security-by-obscurity' and somebody with enough time will be always able to get the encrypted content somehow. But I can try to make that as hard as possible and in the next releases there will also some additional updates here.

stereo display bug

Made a stereo pano with the make_vtour_normal droplet. Generated xml looks OK, as do the two sets of cube faces.
BUT the right eye view has scrambled cube face order whether viewed with VR, anaglyph or monoside = 2 (Chrome/Win10, also chrome dev/android)

Quoted

Made a stereo pano with the make_vtour_normal droplet. Generated xml looks OK, as do the two sets of cube faces.
BUT the right eye view has scrambled cube face order whether viewed with VR, anaglyph or monoside = 2 (Chrome/Win10, also chrome dev/android)

This is unfortunately a bug in the makepano tool related to the maxcubesize setting. The left-side cube images are getting downscaled to that size during the cube-conversion, but the right-side ones not due that bug.

When you check the files of the example you see the left cube-side-images are 2048x2048 and the right ones are 3758x3758.

That problem happens only in the NORMAL droplets, because there the setting maxcubesize=2048 is used by default.

Unfortunately I didn't noticed that during testing because all my test stereo-panos were only ~6000x3000px, which resulted in 1909px cubesizes and so were below that limit...

This will be fixed in the next release of course.

These workarounds would be possible for this case for the moment:

use the MULTIRES droplets (generally recommended)

increase the maxcubesize setting in the vtour-normal.config (e.g. to 4096)

krpano 1.19-pr16

It mainly fixes a license bug that happens in very old browsers.Update: and now also a bug that happens when using multiple krpano viewers on one page. If you have already downloaded version pr16 one hour ago, please download it again.

The bug related to large stereo panos on the NORMAL droplets is also fixed there of course.