I think I understand conceptually how this is happening and can probably have PR for this tomorrow. The hide tool only tags PBVH nodes for being updated when one of the node's own vertices changes…
There's a bug somewhere in the current implementation when there's more than one PBVH node, I'm not yet sure exactly what's causing it.
This allocation is already occurring in the existing code inside init_operation and is cleaned up when the unique_ptr goes out of scope by the GestureData destructor, but I agree that moving…
Ugh, sorry. Don't know how I missed this crash before submitting the PR. Appreciate you taking a stab at the fix.
The order of initialze_cursor_info and then init_operation is actually still needed. This fix would just introduce other errors on the following line:
003489c693
Fix #120701: Overrides: Running Make Override operator in viewport without a selection created duplicates.
From the sculpting side of things, this comment and others in the issue may be helpful in gathering some requirement…
Seems pretty reasonable, I'm sure this will be helpful for people. I don't fully understand the "duplicates" part of the multires neighbors system, I have to look at that to be more confident…
Ah, I think I see how to do this from the documentation - Using mesh::face_corner_prev / mesh::face_corner_next, right?
Updated the keymap so that with RCS enabled, the interactions remain the same (i.e. starting the tool & adding points with LMB and canceling with RMB / ESC)
@nickberckley - I wouldn't describe the current behavior of Line Project as being equivalent to Fair Tangency. The type of projection it's doing is simply moving affected vertices to the plane…
I think there's an issue with the right click select keymap, it works quite differently-- I have to hold down right click for the whole operation and add points with LMB.
Thanks for the…