krpano 1.20

vope · February 5, 2020 at 11:51 AM

Hi Klaus

I work with the german keyboard layout. The logkey is on my layout the circumflex ^ key.
When I show the log window in the browser with the ^ key, and switch back to my code editor start coding it brings my always a ^ at the beginning.
I have to manually delete this circumflexes. Sometimes I forget and that brings me errors im my conde.
Its possible to change the logkey to somewhrere else?

Beste regards
Peter

Sudarchikov Andrey · February 5, 2020 at 12:51 PM

Hi! Klaus.

IMPORTANT

i was wonder that hotspots with destorted="false" become strange (like distorted) in stereoscopic and fisheye projections
Can not find which settings should i change to solve this issue

Thanks in advance!
Andrey

Normal projection (distorted=false)

Fisheye projection (distorted=false)

Sergey74 · February 5, 2020 at 1:01 PM

Quote from Sudarchikov Andrey

Hi! Klaus.
IMPORTANT
i was wonder that hotspots with destorted="false" become strange (like distorted) in stereoscopic and fisheye projections
Can not find which settings should i change to solve this issue
Thanks in advance!
Andrey

I also wrote about this here and here .

indexofrefraction · February 5, 2020 at 1:40 PM

Quote from Sergey74

Ok, I’ll repeat my question again: is this a normal hotspot behavior?
https://panosphera.ru/gallery/bhub7rk/
XML https://panosphera.ru/gallery/bhub7rk/krpano.xml

ok... you see it clearer if you put the hotspots close to the north/south pole

i also see strange hotspot deformations in your lensflares :
https://panosphera.ru/gallery/zuratk…150,-40,130,0,0

... klaus?

klaus.krpano · February 5, 2020 at 9:12 PM

Hi,

Quote from Sergey74

I have one more question. Now my plugin "lensflare" has become strangely behaving in a stereographic projection. If I set a css3d rendering (for hotspots), this does not happen.
Link example https://panosphera.ru/gallery/zuratkul/?…150,-40,130,0,0);

This is unfortunately a known limitation since 1.20 and was necessary to be able to support the non-distorted hotspots also in 'depthmap mode'. That will be changed in one of the next releases. Then there will be internally a special renderer/shader especially for non-distorted hotspots (currently non-distorted hotspots are also just distorted hotspots but automatically rotated toward the 'camera center'). That special render will then also provide other features like pixel-grid-fitting for a sharper rendering and more control about the 2d screen position.

Quote from vope

Its possible to change the logkey to somewhrere else?

Changing the logkey is not possible (it wasn't even easy to support that one key across all systems and browsers), but you could disable the default logkey and use a keyboard event and a custom key - e.g. here using the SPACE key (keycode 32):

Code

<events name="my_custom_logkey" keep="true" onkeyup="if(keycode == 32, showlog());" />

Best regards,
Klaus

McTristan · February 6, 2020 at 8:14 AM

Is it possible to tar & gz the Linux package and not just tar them (or so it appears from the file header)? With every new version I have to gzip the archive as our component heavily relies on extensions. So it expects a zipped tar file by the extension .tar.gz but in reality it is just a tar file with the wrong extension.
When you look in the latest krpano-1.20.4-linux64.tar.gz file you can clearly see that it is not zipped but just tarred (it is a .tar-file). Hope this make sense.

Just check the difference between

tar cvfz FILENAME.tar.gz DIRECTORY/

and

tar cvf FILENAME.tar DIRECTORY/

the first call creates a correct (g)zipped tar file, the second call just a tar-file.

klaus.krpano · February 6, 2020 at 9:40 AM

Hi,

Quote from McTristan

Is it possible to tar & gz the Linux package and not just tar them

What browser did you use to download the files?

The files itself are actually tar-packed AND zipped, but the Chrome browser has a bug, it is unzipping the files automatically during download. Every other browser should be fine.

Here the Chrome bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=83292

Update: the problem should be fixed now (by a by server setting, here for more information).

Best regards,
Klaus

McTristan · February 10, 2020 at 11:39 AM

Thank you for your help.

Now another problems seems to rise with iOS 13.4 (currently in beta). It seems like the gyroscope mode is no longer working correctly (it is just kind of wobbling the image but no real motion) and the VR mode ist no longer working as well. With the latest 13.3.x everything seems to be fine.

I don't know if this will still be a problem with the official 13.4 version but right now it does not seem to be too great :/

klaus.krpano · February 10, 2020 at 2:25 PM

Quote from McTristan

Thank you for your help.
Now another problems seems to rise with iOS 13.4 (currently in beta). It seems like the gyroscope mode is no longer working correctly (it is just kind of wobbling the image but no real motion) and the VR mode ist no longer working as well. With the latest 13.3.x everything seems to be fine.

I don't know if this will still be a problem with the official 13.4 version but right now it does not seem to be too great :/

Hi,

I can confirm this is a bug in iOS 13.4 beta 1.
The acceleration and rotationRate properties of the DeviceMotionEvent are null there.

I have made a minimal example and sent it to Apple (hopefully someone will read it there):
https://krpano.com/ios/bugs/ios13-4-b1-gyro/

Btw - PLEASE reports such bugs also to Apple yourself, the more reports the better!

But if not getting fixed by Apple, a workaround would be possible - krpano can alternatively also use the DeviceOrientationEvent instead of the DeviceMotionEvent, and that one is still working - see here for more:
https://krpano.com/plugins/gyro2/#sensor
https://krpano.com/plugins/webvr/#mobilevr_sensor

Best regards,
Klaus

insideplaces · February 11, 2020 at 11:26 PM

Hello after the upgrade, i'm experiencing some unexpected behavior in Android devices. When accessing a tour, the screen loads with the a huge Enter VR button in the middle of screen, when clicked, loads the VR view but with one side of the screen totally black. I'm following the demotour-apartment example.

Here's some of the screenshots:

Code

https://imgur.com/a/7aulLcE

Code

https://imgur.com/a/suZegVo

I thought it might be the device database, but demotour-apartment works perfectly in this same device...

Tested in Galaxy S6 and Moto E

In iOS devices work as expected... Did someone encountered similar problem and know how to fix?

Taurus · February 19, 2020 at 1:37 PM

Klaus, thank you for your great work!
But there is a problem with the smooth panorama drag mode - mouse=follow
When quickly dragging a panorama, after several repetitions, sometimes an unexpected additional accelerated scrolling of the image occurs - http://vhsystem.ru/moscovsky_inter_no/

Moreover, in my case, this is observed in panoramas obtained from the equidistant 8000*4000 and absent in panoramas of 20000*10000

klaus.krpano · February 22, 2020 at 7:29 PM

Hi,

Quote from Taurus

But there is a problem with the smooth panorama drag mode - mouse=follow
When quickly dragging a panorama, after several repetitions, sometimes an unexpected additional accelerated scrolling of the image occurs

Thanks for reporting, but that's not a bug in krpano.

In your code you have somewhere a 'onviewchange' event that calls 'adjusthlookat(0)' - and that constantly changes the view.hlookat value to be in the range -180 to +180. And that's the main problem, when dragging across the 360 degree around boundary the continuous hlookat changes gets interrupted and e.g. a value like +200 jumps to -160 (=200-360).

Try to remove that adjusthlookat(0) call to fix the problem.

Best regards,
Klaus

Taurus · February 24, 2020 at 2:11 PM

Quote from klaus.krpano

Try to remove that adjusthlookat(0) call to fix the problem.

Klaus, thanks, this completely solved the problem !

klaus.krpano · March 5, 2020 at 3:58 PM

Hi,

there is another minor update with improvements and fixes:
krpano 1.20.5

For all details please have a look here:
Release Notes 1.20.5

Best regards,
Klaus

jeromebg · March 5, 2020 at 4:01 PM

Thanx Klaus !

Tuur · March 5, 2020 at 4:47 PM

Thank you!

Code

&#09;

Tuur

Alexander360 · March 20, 2020 at 12:14 PM

With this latest version, the 'Enter VR' layer button doesn't appear when tours are accessed in an Oculus GO headset? Is anyone else experiencing this problem?

agufon · March 26, 2020 at 6:36 PM

In versions 1.19 and earlier, the browser URL included parameters (for example ... / index.htm? Startscene = 11 & startactions = lookat (37.07, -0.65,80,0,0);) that were updated when the panorama was interacting. This was very useful for sending someone a specific position within a scene, including zoom and all sorts of data.
In version 1.20 this no longer works. It supports the parameters, but not the dynamic interactivity of seeing the panorama position in the URL.
I acknowledge my ignorance and that is why I am a beginner but how could I include this utility in version 1.2?
Thank you.

klaus.krpano · March 26, 2020 at 8:39 PM

Quote

In version 1.20 this no longer works.

Sorry, but that's not true, there were no changes and there is no reason why url parameters shouldn't work anymore...

Please post your example (in a separate thread), maybe you haven't enabled the parameter passing or the deeplinking setting.

agufon · March 29, 2020 at 2:08 PM

Thank you Klaus for your response and interest.
I pass two links to you:

1: http://www.imaginartejuegos.com/descargas/thys….53,79.54,0,0);
In this link you can see that, when moving the paonrama, the URL changes accordingly.

2: http://imaginartejuegos.com/descargas/vtou….53,79.54,0,0);
Instead in this other link, the parameters of the URL remain fixed even if the panorama moves.

I hope I have explained myself.
Regards

krpano 1.20

Participate now!

Users Viewing This Thread