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
When using static pick method in Potree, picking window is not used.
Only when directly hovering within a points rendered area is it picked.
The provided screenshots displays when the mouse is within and a sphere is created on pickPoint hit position.
When pick window works as intended, we would expect all points within specified picking rectangle window to be considered hits. And after this, the closest of those hits would be the one returned as PickPoint.
The text was updated successfully, but these errors were encountered:
I also ran into this recently and found a hacky workaround in case it helps (this is definitely not the solution)
I force the point size to be the same as the desired pick window size during the picking
Additionally I've run into strange issues when using arrays of pointclouds during picking, where the closest point is not picked or no pick is returned at all. The workaround there was to iterate through the pointclouds one by one, noting the hit distances, then choosing the closest. Its marginally slower but at least gives accurate results.
When using static pick method in Potree, picking window is not used.
Only when directly hovering within a points rendered area is it picked.
The provided screenshots displays when the mouse is within and a sphere is created on pickPoint hit position.
I have setup a forked repo based on your example scene
here: https://github.com/fredrik-hjelmaeus/pnext-three-loader-pickwindow-issue
usage: When pointcloud is loaded, sphere will be displayed on any pick point hits.
When pick window works as intended, we would expect all points within specified picking rectangle window to be considered hits. And after this, the closest of those hits would be the one returned as PickPoint.
The text was updated successfully, but these errors were encountered: