Closed jjimenezg93 closed 9 months ago
This issue has been marked as stale by an automated process because it has not had any recent activity. It will be automatically closed in 30 days if no further activity occurs. If this is still an issue please add a new comment with more recent details and repro steps.
Un-stale-ing for MRTK3.
We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!
Describe the bug
RotationAxisConstraint
andBoundsControl
don't work well together in a number of ways. Link to the suggested solution adopted by UXT is inAdditional context
.Examples (see GIFs below too):
X
(both in local and world space), the object will only rotate up to a certain degree, then it'll start rotating back. However, when no axes are constrained, you can rotate the object 360º.Z
axis in local space, you can roll with any edge handle, but you should only be able to do so with handles on the side edges.To reproduce
BoundsControlExamples
.SceneContent > CoffeeCups
and select one of them.RotationAxisConstraint
, bothConstraint On Rotation
andUse Local Space For Constraint
.Expected behavior
Assuming that the object was sliced through the center by 3 perpendicular planes, each edge handle should rotate around the plane it's on, unless it must constraint in world space, as the projection of the rotation might lead to a certain rotation on another axis. Also, the configuration shouldn't allow constraining a single axis, as rotating around the other two axes can achieve the same rotation you're trying to restrict.
Screenshots
Your setup (please complete the following information)
Target platform (please complete the following information)
Additional context
We have fixed this in UXT by using swing-twist decomposition (instead of Euler decomposition) in the constraint and slightly modifying how
BoundsControl
uses it. Still works perfectly fine with Manipulator.