You are not logged in.

css3d hotspot culling

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

vincent-moyosa

Beginner

  • "vincent-moyosa" started this thread

Posts: 5

  • Send private message

1

Wednesday, October 14th 2020, 11:56am

css3d hotspot culling

Hi,

I'm trying to do some advanced custom hotspot stuff. I've created a hotspot with some additional html (added through js) that has `renderer="css3d"`. This all works nicely except that the created boundingbox for this element seems too small. This causes the hotspot to disappear when the center of the hotspot leaves the screen (css `display: none` is added to the div). I've tried the `pixelhittest` attribute but this doesn't seem to change anything.
Is there a way to define a custom size for the bounding box or just disable culling for this element?

vincent-moyosa

Beginner

  • "vincent-moyosa" started this thread

Posts: 5

  • Send private message

2

Wednesday, October 14th 2020, 1:42pm

I just noticed this is only an issue on firefox, on chromium it works as expected.
Edit:
Tested on safari as well and doesn't seem to have culling issues either

This post has been edited 1 times, last edit by "vincent-moyosa" (Oct 14th 2020, 3:21pm)

loki

Trainee

Posts: 72

Location: Berlin

  • Send private message

3

Thursday, March 3rd 2022, 3:07pm

Hi,

I also have this issue with css3d hotspots on firefox only and suspect cube faces, not bounding-box, see video.
All disappearing hotspots get overridden with "display:none" as vincent also reported.

Is there a way to fix this?

Thanks,
Max
loki has attached the following file:
  • culling.7z (176.84 kB - 97 times downloaded - latest: Mar 6th 2023, 8:58am)

klaus.krpano

Administrator

Posts: 13,363

  • Send private message

4

Thursday, March 3rd 2022, 5:09pm

Hi,

do you have a link to that example?

Best regards,
Klaus

loki

Trainee

Posts: 72

Location: Berlin

  • Send private message

5

Monday, April 4th 2022, 10:41pm

Hi Klaus,

while in Firefox the hotspots will be set to display:"none" and pointer-events:"none", I noticed in Chrome the display setting is not changed but also pointer-events:"none" gets set from "auto" to "none".
I believe it has something to do with either tx/ty/tz or ox/oy values. If I change theses values in a drag action, the display:"none" will be set sooner when changing the view (or later depending on final drag values).
I sent the project by mail some weeks ago, but I totally understand should the big update be more important right now.

Best regards,
Max


//edit:
There is a dirty workaround by adding a css class containing "display:block !important;" and "pointer-events: auto !important;" to these hotspots with a for loop in the onviewchange event. I limited the event so it would not fire with each redraw but I guess the performance still suffers a lot?

This post has been edited 2 times, last edit by "loki" (Apr 5th 2022, 1:41am)

Similar threads