krpano 1.20.11

klaus.krpano · December 28, 2021 at 10:13 PM

Hi,

there was a minor update for version 1.20.11 - now it's build 2021-12-28 (no version number change):

Only the pp_light.js and pp_sharpen.js post-processing plugins were updated. On some older Apple GPUs the Light plugin caused strange colors or artifacts when used in combination with a transparent viewer background (due a strange GPU bug or behavior).

Best regards,
Klaus

PanoramicWEB · December 29, 2021 at 1:12 PM

Minor Bug
https://server.panoramicweb.net/demo/blendtest…scene20-10.html Blend working

https://server.panoramicweb.net/demo/blendtest…scene20-11.html only default blend working the others not working

https://server.panoramicweb.net/demo/blendtest/scene.xml same xml using

Best regards

klaus.krpano · December 29, 2021 at 3:27 PM

Hi,

your links don't work (503 server error), but if you use a transparent viewer background in these examples, then this is the reason.

The blending of two transparent panos is a slightly more complex case. WebGL isn't able to do that out of the box, so that transparent-blending is done manually using an extra post-processing step.

And currently there is only the normal cross-blending implemented for this special case.
But if required it would be possible to implement all blending-modes for this case in future versions of course.

There are notes about that in the documentation here:
https://krpano.com/docu/html/#bgcolor

and here:
https://krpano.com/docu/actions/#loadpano.blend

Best regards,
Klaus

PanoramicWEB · December 30, 2021 at 10:38 AM

Minor Bug

Sorry. our server is broken down. i copy new link.

my problem is that zoomblend works in krpano 1.20.10, but not in 1.20.11.

https://www.panoramicweb.net/demo/blendtest…scene20-10.html Blend working

https://www.panoramicweb.net/demo/blendtest…scene20-11.html only default blend working the others not working

https://www.panoramicweb.net/demo/blendtest/scene.xml same xml using

What should I do if I want to change the settings unlike version 1.20.10

Best regards

klaus.krpano · December 30, 2021 at 8:57 PM

Quote from PanoramicWEB

https://www.panoramicweb.net/demo/blendt…scene20-11.html only default blend working the others not working

Okay, I see - it's the setting wmode:"opaque" in your html file. That also results in the transparent background rendering in the html5 viewer and therefore the blending modes are limited to the default cross-blending one (as explained above). Just remove that setting.

Best regards,
Klaus

klaus.krpano · January 13, 2022 at 1:26 PM

Hi,

there another very minor update for version 1.20.11: build 2022-01-13.

It mainly fixes the soundinterface plugin problem when playing a sound a second time again doesn't work,
and adds optional support for cylindrical panos in the make vtour and convert droplets.

Release Notes:
https://krpano.com/docu/releasenotes/#top

Best regards,
Klaus

Loro · January 13, 2022 at 9:49 PM

Quote from klaus.krpano

there another very minor update for version 1.20.11: build 2022-01-13

Thanks Klaus for the fix!

bg360 · January 24, 2022 at 9:53 PM

There was a fix for Bingmaps Plugin: Remove the radar size limitation,
but when should I expect the same fix for Googlemaps?

mypod · January 26, 2022 at 4:45 AM

Hi Klaus
I am struggling with the file structure of the Maps2 example, where krpano is used as main map-viewer with full lat/lng/zoom support. [font='Trebuchet MS, Arial, Helvetica, sans-serif']https://krpano.com/examples/#maps2[/font]

where are the tour.xml and the different panos supposed to be placed for %CURRENTXML%/../tour.xml to work?
Can someone please share the project file for the same?

Really appreciate the quality of the latest update !

Nupsi · January 28, 2022 at 9:19 AM

WOW Can´t wait to test the new overlay- and iFrame-features

klaus.krpano · March 7, 2022 at 6:05 PM

Hi,

another minor update for version 1.20.11: build 2022-03-07.

Best regards,
Klaus

Fernando · April 8, 2022 at 4:37 PM

Thanks very much, Klaus!

ChukA · June 14, 2022 at 3:35 PM

Hi everyone,

i get an issue with the 1.20.11 and IOS 12.4.8 safari 12.1.2

"device.touch" is not detected anymore...

if i change back the tour.js by an old one it works.

nb: if i put device.mobile it's work...

Any idea ?

wfchxhdn · July 4, 2022 at 4:22 AM

Dear Klaus, I’m Cory from China. I want to buy krpano from your website. In order to apply for reimbursement, I need to know whether I can get an invoice after buying krpano1.20.11 and what it looks like. Would you please tell me?
Best wishes to you!
Cory

indexofrefraction · July 4, 2022 at 10:02 AM

krpano uses mycommerce / shareit.com, of course you get an invoice.

wfchxhdn · July 5, 2022 at 3:03 AM

Quote from indexofrefraction

krpano uses mycommerce / shareit.com, of course you get an invoice.

Thanks a lot!

philippeK · November 4, 2022 at 12:15 PM

Hello,

Last decade Web has changed significantly: flash and IE are dead, WebGL 2.0 is broadly supported by all browsers, WebGPU & WebXR are on the way, JavaScript evolved a lot, WebAssembly has arrived, etc.

I use Krpano for one of my client in France and I'm curious klaus.krpano how do you see the future of Krpano ?

PanoramicWEB · November 5, 2022 at 6:39 PM

we can support krpano, SAAS system for yearly payment and Klaus can focus all his time to develop KRPano i think.

klaus.krpano · November 8, 2022 at 11:51 AM

Hi,

Quote from philippeK

Last decade Web has changed significantly: flash and IE are dead, WebGL 2.0 is broadly supported by all browsers, WebGPU & WebXR are on the way, JavaScript evolved a lot, WebAssembly has arrived, etc.

I'm following actively all these development of course!
For krpano and also just for personal interest.

Some notes:

WebGL 2.0 is nice and makes implementing some thing easier - and in krpano 1.21 I'm using it optionally for some shaders (with fallbacks for WebGL 1.0), but at the moment I think it's still too early for 'WebGL 2.0-only'. This would unnecessarily exclude too many devices and browsers. Depending on the needs the same that can be done in WebGL 2.0 can be also done also with WebGL 1.0, even when that requires more internal work.
That means there is currently no advantage or disadvantage of using WebGL 2 in krpano. But if someone whats to use it, in krpano 1.21 there is option to enable the WebGL 2.0 API.
WebXR is already supported, but not all 'special' features from it, more to come here.
'JavaScript evolved a lot' - yes, but many things are just syntactic sugar, and nicer looking code is no reason to through away compatibility.
WebAssembly is super interesting, but I don't see a need for it inside krpano. There is no heavy processing in krpano that could profit from a WebAssembly implementation.
WebGPU - even more interesting, with it implementing certain things could be much easier and faster. But first here a fixed standard and broader support is required.

Beside these notes - note that these are all 'developer-features', not really relevant for the end-user. So far the outcome should be more important than the tools that were used to build it ;-).

Quote from philippeK

klaus.krpano how do you see the future of Krpano ?

More capabilities/features and especially easier usage/tooling.

With the next krpano 1.21 version, which is mainly an update for viewer-side, I'm preparing parallel also a lot for krpano 2.0, which will be mainly a tools-side update.

Best regards,
Klaus

sakshi · November 9, 2022 at 1:40 PM

Quote from klaus.krpano

Hi,

I'm following actively all these development of course!
For krpano and also just for personal interest.
Some notes:
WebGL 2.0 is nice and makes implementing some thing easier - and in krpano 1.21 I'm using it optionally for some shaders (with fallbacks for WebGL 1.0), but at the moment I think it's still too early for 'WebGL 2.0-only'. This would unnecessarily exclude too many devices and browsers. Depending on the needs the same that can be done in WebGL 2.0 can be also done also with WebGL 1.0, even when that requires more internal work.
That means there is currently no advantage or disadvantage of using WebGL 2 in krpano. But if someone whats to use it, in krpano 1.21 there is option to enable the WebGL 2.0 API.
WebXR is already supported, but not all 'special' features from it, more to come here.
'JavaScript evolved a lot' - yes, but many things are just syntactic sugar, and nicer looking code is no reason to through away compatibility.
WebAssembly is super interesting, but I don't see a need for it inside krpano. There is no heavy processing in krpano that could profit from a WebAssembly implementation.
WebGPU - even more interesting, with it implementing certain things could be much easier and faster. But first here a fixed standard and broader support is required.

Beside these notes - note that these are all 'developer-features', not really relevant for the end-user. So far the outcome should be more important than the tools that were used to build it ;-).

More capabilities/features and especially easier usage/tooling.
With the next krpano 1.21 version, which is mainly an update for viewer-side, I'm preparing parallel also a lot for krpano 2.0, which will be mainly a tools-side update.
Best regards,
Klaus

Display More

Thanks for your hard work. I really appreciated your support.

Please make next release soon.

Participate now!