Posts by klaus.krpano

The fakedevice setting is still there and working as before...

Otherwise you can also manually change the device object (via actions or JS), but these changes always need to be done before the device object or settings will be actually used to load or filter something.

Ja, ab der nächsten Version (in Kürze), wird es ARM64 (Apple-Silicon) Support für alle Platformen geben.

Hi,

I have also seen the news about the new HTML-in-Canvas API and it does indeed look very interesting!

It uses an interesting approach by moving an invisible dom element below the actual mouse cursor to trigger interactivity, but I'm not sure yet, how this works with WebXR rendering where no cursor is...?

Texture-update performance will be also very interesting. Hopefully, the HTML/canvas rendering is also done on the GPU, then it could be just a texture ref and very fast. If not, large-textures updates might be still problematic...

I will have a look of course and do real tests in future, then I can say more about it. But generally it could be very usable, html-to-canvas is along awaited feature.

Best regards,
Klaus

Hi,

this is not anti-aliasing, this is wrong (too low) rendering resolution...

In krpano there is a detection and workaround for very old Android devices that weren't handling HiDPI cases (devicePixelRatio > 1.0) correctly, and it seems your device is somehow getting into this case...

Will check that further, I think that special case handling can be already removed...

Best regards,
Klaus

Hi,

the next krpano release will include an Apple-Silicon version (and also ARM64 versions for all other platforms).

Best regards,
Klaus

Yes, the next krpano release (soon) will bring ARM support for all platforms.

Please post a link to your example.

Quote from Visiolab

The issue still the same, however i think i find the problem, it seems related to the presence/absence of the width and height attributes on the root tag of the svg file content

This is a common browser issue - SVG files without explizit size often cause problems. The exact behavior depends on the browser. Some browsers uses fallbacks by using the viewbox as size-source, others just use size 0, which then makes the images invisibly small...

krpano is loading the SVG files as images, so it depends on the browser behavior. And there is also a difference if that image will be uploaded as texture (WebGL hotspot rendering) or insert into the HTML-DOM as CSS3D-rendered hotspot.

So for a consistent behavior it would be good, that each SVG file has width/height settings inside it.

If you know that the layout will not change later, you could disable flowchildren later, e.g. in the onover event before doing the animation. The layers will keep their current position when disabling it.

Hi,

do you have a link to show the issue?

What krpano version?

You could try disabling post-postocessing by set the lensflare exposure setting to false, but that normally that shouldn't matter...

Best regards,
Klaus

Hi,

without hit-testing it is not possible to detect if a hotspot is before or behind a 3D-model.

And hit-testing should be actually very fast, krpano uses a very efficient BVH-tree for intersection testing.

Best regards,
Klaus

Hi,

what device is this?

But setting the webglsettings embedding should definitely work:

krpano.com - Documentation - Embedding into HTML

How do you set it?
Correct would be in the embedpano call:

embedpano({..., webglsettings:{antialias:true}});

But even with disabled anti-aliasing, there should be no jagged edges in the pano images, the anti-aliasing mainly only effects hotspots edges... So maybe the actual problem is something else...

Best regards,
Klaus

HDR and WebGL is an interesting topic, but I must admit I don't know yet how far and wide the browser support it. And then about how to setup the whole pipeline... (hdr input images?)

But for OLED, supporting the P3-colorspace might be also interesting topic and probably easier to setup (maybe that can be already added to the next release, will have a look). That means try exporting from RAW to P3 instead of sRGB, set the krpanotools profile setting to 'copy' to keep it in P3, then enabling the P3 support should be only one flag in the viewer.

Quote from PanoramicWEB

klaus.krpano is krpano development finish?

Of course not, there still a lot to develop.
I know it's been a while since the last release, but I'm working on it every day.

Quote from herrpedro

can we add a plat in a hotspot ?
like.. a splat of a small thing

Currently not, but intentionally, the current focus is rendering performance and stability on mobile/vr devices. The number of splats is already pretty limited, so having scene+hotspots as splats could be quickly too much.

Best regards,
Klaus

Hi,

there is a small misssunderstanding: with shortestway=false, it doesn’t take the ‘longest’ way around the sphere, it just changes from the current value to the given one. This way you can fully control the animation, e.g. do multiple loops by using large values.

Best regards,
Klaus

Hi,

it depends on what tiles you mean...

Tiles for a cube pano - first re-tile the cube-sides, then convert the cube to sphere.
Tiles for a sphere pano - just re-tile.

In case of multiresolution images, only the largest level would need to be re-tiled.

Retiling (merging) and cube/sphere conversion can be done using the krpano tools:

krpano.com - Documentation - krpano Tools

Best regards,
Klaus

Hi,

according to the information here:

https://map.shapefruit.de/styles/osm-bright.json

this might work (basically just use the tile url from there and adopt name/description and attribution):

<krpanomaps_tileprovider name="osmbright"
        description="OSM Bright"
        maptype="osm"
        tileurl="https://map.shapefruit.de/styles/osm-bright/{z}/{x}/{y}.png"
        attribution="Copyright OpenStreetMap contributors - Generated by Dbtc"
        multiresthreshold="-0.4"
        />

Best regards,
Klaus

Hi,

I have checked this in detail now: right there is a problem here related to a changed Chrome behavior...

In older Chrome version there was either 'Android' or 'Android Mobile' in user-agent device information - but no 'Mobile Safari'! In newer Chrome versions there is now only 'Android' and the 'Mobile Safari' additionally for mobile devices.

The current krpano version checks the screensize in case of 'Android' + 'Mobile Safari', because that was used in the Chrome device simulator - and there mobile/tablet decision depends if the smaller screenside was below 480.

The next release will have an updated behavior without that special 'Mobile Safari' workaround.

Best regards,
Klaus

Hi,

it also depends if that tablet even can be detected as tablet - and that depends on the actual tablet and browser:

• iPad's typically can be detected as tablets (even in Desktop mode)
• Android tablets typically too (but probably not in Desktop mode)
• Windows tablets typically can't be detected as tablets.

Best regards,
Klaus

Hi,

try that:
- first start the MAKE VTOUR droplet
- and then drop the images into it

When dragging directly on the droplet, the MacOS system could sometime strangely interfere if the access is not allowed...

Best regards,
Klaus