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
relatedly, it uses a very 'greedy' approach to detect which group to slice: the world-aligned BB of the groups are used. In a more fleshed-out scene, with a lot of grouping going on, it's hard to intuit what the tool will be cutting.-> I fixed this for the hand tool. Having a hard time finding where the branch has gone (probably deleted after merge?) I'd suggest maybe even using the same hover detection as the normal cutting tool: only when actually hovering a polygon.
The text was updated successfully, but these errors were encountered:
@naam00 I think I've got a bit closer on this one.
Your code changed the method SelectMeshAtPosition.
Plane subdiv uses selector.hoverMeshes
selector.hoverMeshes is derived from touchedMeshIds
Selector.TryHighlightingAMesh modifies touchedMeshIds using param "nearestMeshId"
nearbyFaces, nearestMesh are passed to TryHighlightingAMesh in SelectMeshAtPosition as this parameter...
(the latter is used only if former is empty)
nearbyFaces comes from spatialIndex.FindFacesClosestTo
nearestMesh comes from spatialIndex.FindNearestMeshTo
Soooooooo! I think we just need to do something similar to whatever you did previously with FindNearestMeshTo to FindFacesClosestTo
Writing all this here as there is 0 chance I will remember it in 5 minutes...
From @naam00 on #34 :
The text was updated successfully, but these errors were encountered: