MenelvagorMilsom
commented
5 years ago A mentor at the Berlin hack mentioned that a customer was looking for behaviour like this. They wanted the grabbable to be fixed in place, until you moved your hand beyond a threshold, after which the object would jump to your hand position and and you could manipulate as usual.
It seems like if we make the size of this initial deadzone configurable, they may be able to implement the behaviour they were looking for. Let me know if it makes sense to do this here or elsewhere.
Zee2
IssueSyncBot
Filing on behalf of a partner, who was using a bounding box and noticed some odd behavior both on device (HL1) and in simulator.
The issue came up initially in the simulator, where just clicking to "pinch" an object that had a bounding box would also move it toward the camera a little. This is caused by how the simulation code works (where at the beginning of the gesture, the index tip has a different position and rotation compared to the index tip compared to the end). This could be pretty trivially fixed by updating the joint pose data to have the same index tip (no motion, yay!) but this would probably end up masking the underlying issue, which is that maybe there should be some initial manipulation deadzone, which must first be passed before things start moving. (Or maybe this exists and we need to just add docs on this).
They noticed similar issues on HL1 where using the pinch gesture to type would also slightly shift the keyboard itself or the content around, which isn't super helpful (you're trying to interact and it's moving subtly as you're interacting)