You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for all of the work on this tool, it's been absolutely instrumental on a big project I've been working on 😄
Describe the bug
Mouseover detection on objects works perfectly until the map is resized. Afterward the behavior suggests that the raycaster camera hasn't synced up with the new dimensions of the map. In order to trigger the mouseover detection, the cursor has to be some number of pixels away from the object.
To Reproduce
This can be reproduced in the latest release (v2.2.7) by running examples/01_basic.html as seen in this clip:
raycastingIssue.mp4
Additional context
I believe a related issue was described in #383 . That issue mentioned a workaround of manually creating a new cameraSync whenever the map resizes, which I will try. Nevertheless, if this is a bug in the tool, I wanted to document it here with a simple to reproduce example
The text was updated successfully, but these errors were encountered:
Thank you for all of the work on this tool, it's been absolutely instrumental on a big project I've been working on 😄
Describe the bug
Mouseover detection on objects works perfectly until the map is resized. Afterward the behavior suggests that the raycaster camera hasn't synced up with the new dimensions of the map. In order to trigger the mouseover detection, the cursor has to be some number of pixels away from the object.
To Reproduce
This can be reproduced in the latest release (v2.2.7) by running examples/01_basic.html as seen in this clip:
raycastingIssue.mp4
Additional context
I believe a related issue was described in #383 . That issue mentioned a workaround of manually creating a new cameraSync whenever the map resizes, which I will try. Nevertheless, if this is a bug in the tool, I wanted to document it here with a simple to reproduce example
The text was updated successfully, but these errors were encountered: