krpano 1.22 - Reactive APIs, ThreeJS 3D Plugin, krpano Maps, Improved Javascript APIs, Custom Encryptions

    Quote from PanoramicWEB

    i find small bug. But I don't know why. if panora have stl , like that error
    https://demo.panoramicweb.net/download/krpanoerrovideolow.mp4

    that is probably the same as here

    Post

    RE: sluggish loading of tiles & "shadow" artifacts

    Hi,

    I think the problem has been found: There was a texture caching issue (only for 3D model cubemaps) where a texture was reused but with the wrong mipmap filter state, and this caused mipmap levels to be temporarily used with incorrect/old texture data.

    As workaround try adding this line anywhere in your xml:

    (Code, 1 line)



    In the next release 1.22.4 this bug will be fixed.

    Best regards,
    Klaus
    klaus.krpano
    January 1, 2025 at 10:19 AM
    Quote from klaus.krpano

    Sorry, I can't reproduce that... did the same Linux tests now and in my case all mouse button values are correct...

    Hi Klaus,

    I uploaded my test case: [redacted]

    My console output: [redacted]

    The first click is a left click, the second click is a right click and the third click is a middle click. "mouse.button" is correct for both left and middle click, but not for right click.

    "mouse.leftbutton", "mouse.middlebutton" and "mouse.rightbutton" are always "false". However, I just checked this with krpano 1.21 with the same result. This might be related to the fact that I don't actually trigger those clicks with a mouse device, but via touchpad gestures. Not sure, if this is the intended behavior.

    Kind regards,
    Christian

    ----

    Solution: For the time being, you might be better off using the native JavaScript property (https://developer.mozilla.org/en-US/docs/Web…useEvent/button).

    Edited once, last by ctt360 (February 13, 2025 at 9:09 AM).

    • New
    • Official Post

    Hi,

    while version 1.23 is still in work, here in the meantime a minor bugfix release for version 1.22:

    Best regards,
    Klaus

    krpano 1.22.4 (2025-02-24)

    • New: krpano Testing Server - new -coisolated command line setting to enable the crossOriginIsolated state.
    • New: Makepano Tool - make the scene names in the xml lower-case by default. Therefore a new [BASENAME_LOW] xml template placeholder was added (report).
    • New: depthmap_navigation.xml - use additionally also the E-key for moving down.
    • Fix: There was a texture caching issue were parts of old images were temporarily visible when blending between Depthmapped-3D-Models with cubical images (report).
    • Fix: If a layer or hotspot was removed during a pano/scene change, then the layer/hotspot object was no longer available in the ondestroy event (report).
    • Fix: krpano Maps and all maps-examples - update the basemap.at urls (report).
    • Fix: The getxml() function was wrongly always including the capturewheel setting, even if it had the default value.
    • Fix: ThreeJS Plugin - add support for the view.rx / ry settings.
    • Fix: When the ThreeJS Plugin was included, then the hotspot setting twosided=false wasn't working.
    • Fix: The Shadow Floor from the ThreeJS Plugin was writing to the depthbuffer and so causing that krpano hotspots would be hidden if behind it.
    • Fix: Certain bgroundedge values were not working in the Safari browser for WebGL hotspots (a Safari bug).
    • Fix: The hotspot raycast hit-testing wasn't working when using viewing offsets (e.g. when using dollhouse views).
    • Fix: If loading a .obj 3D-Model as depthmap that doesn't contain textures and also not using a pano-image as texture, then the loading never finishes and the viewer seems to be hanging.
    • Fix: Some HTML layers (content depended) with autosize enabled, didn't show up when inside other layers (report).
    • Fix: vtourskin.xml - deep-linking didn't work when skin_setting.webvr was disabled (report).
    • Fix: The layers/hotspots capture=false setting didn't work when using the follow control mode (report).
    • Fix: Improved embedpano() passQueryParameters security: data-urls and external urls are generally not allowed as parameter values anymore and urls for the xml parameter are limited to be within the current folder structure.
    • New
    • Official Post

    Hi,

    krpano 1.22.4 was been updated again (now build 2025-02-28).

    The embedpano() setting passQueryParameters:true was been removed for security reasons to generally avoid the possibility for cross-site-scripting.

    Additionally there is also an update for version 1.20: krpano 1.20.12 with the same change/fix. This is for the case if updating to 1.22 is not possible due license- or compatibility-reasons.

    More details here:

    Thread

    Warning if still using passQueryParameters:true

    Hi,

    Warning: if you are still using passQueryParameters:true in the html file, it is highly recommended to either change it to passQueryParameters:false or to update to the latest krpano versions!

    This feature was originally be added in the Flashplayer times (as a replacement for SWFaddress) to allow 'deep linking' (e.g. generating URLs that link to specific scenes and views), but it didn't restrict or filter the values that were passed and therefore could also be abused for Cross-site-scripting…
    klaus.krpano
    February 28, 2025 at 5:06 PM

    Updating to one of these versions is recommend!

    Best regards,
    Klaus

    • New

    I don't know if it's a bug or a feature. It happened by chance, if you pass a value (rx, ry, rz) to a hotspot that is not a number, then it behaves like a layer. Example

    Code
    <krpano>
	<preview type="grid(cube,64,64,512,0xCCCCCC,0x444444,0x999999);" />
	<view fov="100"/>
	<hotspot name="test" type="container" distorted="true" enabled="true" edge="leftbottom" width="500" height="500" bg="true" bgcolor="0x000000" bgalpha="0.5" bgborder="1 0x00FF00" bgbordermode="inside" bgborderblend="true" bgcapture="true" onclick="set(rx, NaN);"/>
</krpano>

    translation difficulties *huh*

    • New
    • Official Post

    Hi,

    versions 1.22.4 and 1.20.12 have been updated again: now build 2025-03-06.

    The passQueryParameters setting has been improved. The values of allowed parameters are more restricted now and now not even theoretical possible injecting cases should be possible anymore, especially in version 1.20.12, which was less secure compared to 1.22.4 before.

    Btw - if using Panotour Pro built tours with deep-linking, there the passQueryParameters can be changed to:

    Code
    passQueryParameters="startscene,s,h,f"

    to keep the deep-linking working and make the viewer secure against cross-site-scripting.

    Best regards,
    Klaus

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login