Posts by klaus.krpano

Hi, yes, is planed and already in work.

The pantospot() function is just calling the panto() function and this one is tweening the zoom.

See here the plugin source:
krpano.com - View Source

Quote

Could we have a zoomtospot(name,zoom) action ?

Yes, either just call panto with the spot coordinates,

or add a function like this:

plugin.zoomtospot= function(spotname, zoomlevel)
{
	var spot = spotArray.getItem(spotname);
	if (spot)
	{
		plugin.panto(spot.lat, spot.lng, zoomlevel);
	}
}

or - extend the pantospot function with an optional zoomlevel parameter:

plugin.pantospot = function(spotname, zoomlevel)
{
	var spot = spotArray.getItem(spotname);
	if (spot)
	{
		plugin.panto(spot.lat, spot.lng, zoomlevel != undefined ? zoomlevel : spot.zoomlevel);
	}
}

Yes - e.g.

tween(layer[map].zoom, ...);

krpano.com - Plugins - krpano Maps Plugin

Thanks!
Will be fixed in 1.22.3.

Hi,

add renderer="webgl" to the <hotspot>.

Textfield hotspots are using a CSS3D renderer by default and the blending possibilities are limited with that.

Best regards,
Klaus

The 'resource needs' between the krpano versions should be the nearly the same, especially related to WebGL resources. So that might be not the reason for your problem...

Also note: depending the browser the number of WebGL contexts can be limited, especially on mobile devices, e.g. to just 2 contexts. In such case, when creating a new one, the old one loses its rendering context (and that message appears).

Depending what you need or do, you could try using only CSS3D rendering (without WebGL).

E.g. to create a krpano layer without WebGL:

<layer ... 
    type="krpano" 
    krpanoembedsettings.object="{webgl:false}"
    />

More information here:
krpano.com - Documentation - Embedding into HTML

What was the previous version?
Which Android devices?
Link to your example?

Thanks for reporting!

Right, images shouldn't be affected by this setting.
This will be fixed in the next release (1.22.3).

Please try if setting the sameorigin embedding setting to false helps here:

https://krpano.com/docu/embedpano/#sameorigin

embedpano({..., sameorigin:false});

The only reason I could think of here would be that the server does not allow access to it (CORS).

For more, post a link to your example.

Yes, it's called 'bounding box':

krpano.com - Plugins - ThreeJS

What popup?
How does it work?
E.g. how and where does it gets its text?

Hi, show a link to your example or your implementation details.

Hi, here a similar example where the view moves to the (in this case double-)clicked geometry position:

krpano.com - Examples

Hi,

right, this is a bug.

The not working layer single/double-clicks events and the global doubleclick event have the same reason.
Both is fixed now for version 1.22.3.

Best regards,
Klaus

Hi,

that's possible, but only with a specific setup:

1. the main viewer need to have a transparent background, therefore in the embedpano() call the bgcolor setting need to be set to transparent:

embedpano({..., bgcolor:"transparent"});

2. then the main viewer will get no pano <image> and keeps empty, only the hotspots can be defined. The overlapping pano images need to be defined in separate krpano layers and need to have set parent="BGLAYER", e.g.

<layer name="pano1" type="krpano" parent="BGLAYER" zorder="1" ... />
<layer name="pano2" type="krpano" parent="BGLAYER" zorder="2" ... />

This way the panos are drawn behind the hotspots, can optionally use CSS blend modes for mixing and the hotspots are above that and unaffected by any blending-modes.

Best regards,
Klaus

Hi, right, the Quest 2 is too slow for complex ThreeJS content - the car 3D-model is big and complex and the ThreeJS fragment shaders are also not the fastest ones...

It's not perfect on the Quest 3 either, but it's quite usable there.

Although it should be possible to optimize the example for performance, e.g. a less complex 3D-model, smaller textures and lightmaps, simpler and faster shaders, but then also the visual quality would be a bit more worse.

Hi, that's fixed now in version 1.22.2:

Post

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

Hi,

another bugfix release: krpano 1.22.2

• New: The textfield template supports now also linking to events (and using an expression for the resulting content)
• New: The ThreeJS Sun Light supports now an optional custom center position for the shadowmap (atview=false). Additionally there is new shadowmaphelper setting to visualize also the position and range of the shadowmap. And the Sun Light helper is now dragable.
• Fix: Static defined linking to attributes of the same element was not working (report

…

klaus.krpano

November 20, 2024 at 8:33 PM

Hi,

there is a new release:

Post

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

Hi,

another bugfix release: krpano 1.22.2

• New: The textfield template supports now also linking to events (and using an expression for the resulting content)
• New: The ThreeJS Sun Light supports now an optional custom center position for the shadowmap (atview=false). Additionally there is new shadowmaphelper setting to visualize also the position and range of the shadowmap. And the Sun Light helper is now dragable.
• Fix: Static defined linking to attributes of the same element was not working (report

…

klaus.krpano

November 20, 2024 at 8:33 PM

It fixes a bug from 1.22 and 1.22.1 related to arrays, which could cause strange behaviors. Maybe that is also relevant here.

Best regards,
Klaus

Hi,

another bugfix release: krpano 1.22.2

• New: The textfield template supports now also linking to events (and using an expression for the resulting content)
• New: The ThreeJS Sun Light supports now an optional custom center position for the shadowmap (atview=false). Additionally there is new shadowmaphelper setting to visualize also the position and range of the shadowmap. And the Sun Light helper is now dragable.
• Fix: Static defined linking to attributes of the same element was not working (report).
• Fix: Adding a value to an existing krpano array-item, that has the the index 0, wrongly created an new auto-named array-item (report).
• Fix: Cubemap panos with objectsize=0 weren't displayed.
• Fix: Panos with a 3D-model as depthmap and rendermode="depthmap" had a wrong origin.
• Fix: screen-based raycasts were not working correctly with external renderers (e.g. ThreeJS) when no hotspot had the hittest setting enabled (report).
• Fix: The <if> xml element didn't work inside non-root-level-elements.
• Fix: Depthmap hittestmode="gpu" was not working.
• Fix: Using depthmap-hittesting and hotspot-hittesting the same time was not working.
• Fix: drag3d.xml - support 3D dragging also when using view offsets.
• Fix: Enable the VR position tracking also in the ThreeJS Environment Maps, Tuscany and Open Source Plugin examples (report).
• Fix: Spherical images for the ThreeJS environment texture were using the wrong color-space (causing washed-out colors).
• Fix: The leveling tool in the krpano Tools app was not working (report).
• Fix: <a href="..."> links inside textfields were not working with touch controls.
• Fix: Some typos and missing links in the documentation.

Additionally, the ThreeJS Tesla example has been updated:

• It supports VR now - if you have a Meta Quest 3, have look , the proportions should look quite realistic.
• There are multiple different pano-environments to test different colors and lightnings.
• And the materials of the car 3D-model can be interactively changed.

Best regards,
Klaus