Posts by San7

Quote from klaus.krpano

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

Klaus, thanks for the quick reply!
If the verification is really fast, then I can use it.

Quote from Tuur

I think, perhapse, renderer svg makes problems.. try a pic and renderer webgl.
((?) i'm not on desktop now..)

Tuur

If depthmap.hittest="true" , hotspots are hidden.
If depthmap.hittest="false," they are visible.
However, "hittest" takes up performance, and I wouldn't want to enable it.

Points are created dynamically based on the camera coordinates in the model, and all points are created simultaneously for all panoramas.
I created a plugin for selecting the required ones.
You can set hittest="true" and depthbuffer=true to hide the points outside the models. But hittest="true" is required.

<style name="navi_hs3d" type="image" keep="false" capture="false" alpha="0.5" distorted="true" depth="0" depthbuffer="true" renderer="svg"
url="%VIEWER%/xml/hs_r.svg" width="100" height="100" scale="0.5" rx="-90.0" ry="0.0" rz="0.0"
linkedscene="" route="" route2="" scen="" dist="" ah="" av="" creat="false"
onover.addevent="scale= 0.55; alpha=0.8; "
onout.addevent="scale=0.5; alpha=0.5;"
onclick="if(!select_hs, tour3d_loadscene(*linkedscene,*tx,*ty,*tz, 0 ); );"
ondown=" "
/>

Quote from kme

you can set enabled="false" when they get behind a wall

But is this with hittest="true"?
If hittest="true" and depthbuffer=true, then the hotspot is already insensitive.
hittest="true" wastes resources, which is undesirable.

Quote from kme

Something like this:

https://krisoft.gumroad.com/l/bpcaa

But in the example, the hotspots behind the wall are mouse-sensitive.

Hi!
If I set depthbuffer=true in a hotspot, it hides behind the model but remains mouse-sensitive.
How can I disable sensitivity if it's out of view?

Quote from jeromebg

Or just replace vtourskin_hotspot.png file in the skin folder ;)

Hi! The native arrow style specifies scale, not size, and the new image will be either larger or smaller if the size doesn't match the original arrow. Keep this in mind.

Quote from sg63

Are there any courses, walkthroughs or tutorials available for krpano?

After using krpano at a basic level a decade ago I've come back to it with a more determined approach. Things seem to have changed and sadly, my coding skills are negligible.

By this I mean I don't understand basic syntax - everything is effectively new to me. I appreciate that the documentation is thorough but it's not something i can get my head round just yet.

I find I'm not learning from cutting and pasting - often things go wrong and I don't know why.

I'm familiar with html and css but that's about it - so I'm not totally unfamiliar with the idea of coding. Which I know is hardly relevant here :)

So if anyone could kindly point me in the right direction I'd be very grateful!

Display More

Hey, there's not much information online about learning Krpano.
The examples on this website are really helpful. The key is to analyze how the code works and run more small test runs, focusing on analyzing individual actions, events, layers, and interactive points. It's very helpful!
Don't be lazy, you can do it.

Quote from khanamiryan

Hi,

I have a panorama with prealign values set (the image is rotated/leveled). When I click on the panorama and create a hotspot using mouse.x and mouse.y with prealign="true", the hotspot appears at the wrong position.

I understand that mouse.x/mouse.yreturns view-space coordinates, but a hotspot with prealign="true" expects image-space coordinates (before the prealign rotation).

Is there a built-in way to convert view-space spherical coordinates to pre-aligned image-space coordinates? Or what is the correct math/rotation order to do this manually?

I am doing something like that.

Code

	//for example krpano.prealign === "0|90|0"
	const hs_new = krpano.actions.addhotspot();

	let mx = krpano.mouse.x;
    let my = krpano.mouse.y;
    
    const {x,y} = krpano.actions.screentosphere(mx, my);

	hs_new.ath = x;
	hs_new.atv = y;
	hs_new.prealign = true;

Display More

The hotspot appears offset from where I clicked. What is the correct approach?
removing prealign is not possible for my situatiuon. I am sending the coordinates to the backend and saving them. Users can add prealign (or rx/ry) of image dynamically, so I need to keep their original places.

Thanks!

Display More

Hi, I did this test.

<image prealign="0|90|0" >
<events name="test" keep="true" 
    onclick="screentosphere(mouse.x, mouse.y, toh, tov); js(console.log(get(toh)));"  
/>

Clicking on the screen next to the hotspot displays the correct ath coordinates.
I created a dynamic hotspot, copied it to the tour, and after rebooting, it snaps into place correctly without prealign="true"
I think prealign is needed for hotspots that were created before alignment.

Hello everyone! Sorry for not making any changes in a while.
The menu has been updated to v2.31.

• Fixed errors with automatic thumbnail display.
• Fixed errors with placing a marker on the thumbnail of a viewed panorama.

Quote from jeromebg

Hi,
I'm working on a tour for a client who is using this plugin.
How to activate the menu item when navigating between the scenes ?
interactive is set to true.
Thank you

Hi, yes, there is still such a bug, I am making corrections

Quote from lnailoveme

Hi, I have a question about the FloorPlan plugin.

It seems that changing the heading_rad value inside the POINTS layer has no effect on the radar direction.

Example:

Code

<!-- PLANS -->
<layer name="plan_1" style="style_plan" capturewheel="false"
       url="%FIRSTXML%/FloorPlan/plan/bando.webp"
       title_fp="MAP"
       pit_width="62"
       radar_scale="0.94"
       heading_rad="270"
       plan_ur="bando.webp" />

<!-- POINTS -->
<layer name="plan_1_1" style="pointflpl" parent="plan_1"
       capturewheel="false" x="392" y="-620"
       linkedscene="scene_flycam03"
       title="flycam03"
       heading_rad="100" />

Display More

Even when I change the POINT’s heading_rad="100" to any value, the radar direction does not change in the viewer.

Only the heading_rad in the PLAN (plan_1) affects the radar, but the individual POINT heading is ignored.

Is this the expected behavior?
Should the radar direction be controlled by the POINT’s heading_rad?
Or is there another parameter that I need to change?

Please let me know how the plugin is supposed to handle per-point heading.

Thank you!

Display More

Hi,
No, the heading only applies to the entire floor plan, not to each point.
First, align all panoramas in the same direction using the Krpano tools or the plugin.

Then you can apply the north correction to the plan (heading radar) —the radar will adjust accordingly.

Quote from klaus.krpano

Hi, is fixed now:
https://krpano.com/docu/releaseno…123#krpano123_2

Hi, Klaus! Thanks for the quick fix!

Quote from indexofrefraction

how are you doing it now ?

Hi!
1. I set up a hotspot (a map with areas) in 3D coordinates
2. I calculate x y taking into account the scale factor (pixelwidth/imagewidth)
3. I get 3D coordinates of the point taking into account rotations along the axes rx ry rz from x y locally on the hotspot (the code in js was written by ai Grok)
4. I set the offset for the point by tx ty tz as for the hotspot and get 3D coordinates of the point
5. I get ath atv spacetosphere(tx,ty,tz);
It was possible to leave 3D coordinates but not all polygons are visible
I do this for each point in the coordinate array and create polygonal hotspots

If I put 1001 everywhere, the polygon is also not visible

Thanks to everyone for the ideas and tips. Brain strain + artificial intelligence helped me solve the problem

Quote from indexofrefraction

maybe try to disable fill ?

what happens if you create a filled 3d polygon and not all points are on the same plane ?

In the example all the points have ty=1000, but if you change the value of one of them to 1001, the polygon will become visible.
I think it shouldn't be like that, it should always be visible

points3d="-3064,1001,-524,-2953,1000,-172,-2443,1000,-334,-2551,1000,-687"

Hello everyone! There is such a polygon

<hotspot name="p1" keep="true"  fillcolor="0xffff00" points3d="-3064,1000,-524,-2953,1000,-172,-2443,1000,-334,-2551,1000,-687" />

but I don't see it.. ? Is it just me or everyone? Please try.
if i change 1000 to 1001 for example it will appear ...

Quote from indexofrefraction

you'd need a get_picture_coords_from_hotspot_to_space(hotspot, x, y) function :)

tricky ... but possible ... (but don't ask me) :D

If there was such a function in the arsenal of krpano, it would be useful

Quote from indexofrefraction

ok, thats not a layer, its a distorted / rotated hotspot placed by ath/atv.

layertoscreen is most likely not working in this case.

mathematically it would be possible to get ath/atv as 3d coordinates (spheretospace)

then add the position vector, then use spacetosphere to get the target points ath/atv

problem is how to get the position vector ;)

its your picture space coordinates, but rotated by rx/ry/rz ...

Display More

to combine the image with the ground, you often have to rotate the hotspot, scale and rotate it along all axes. Probably, you need to calculate the position of each point in 3D space taking into account the scale tx tz rx ry rz of the hotspot