Closed radicalad closed 9 months ago
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 problem
When a
Solver
is set up at edit time, it will snap to its goal orientation at run time. However, when instantiating, or enabling a previously disabledSolver
, theSolver
will "solve" against whatever its current orientation is.Describe the solution you'd like
While the current behavior can be desirable at times, it would be nice if the
Solver
had a "snap to goal on enable" option. This would give flexibility and allow to easily mimic the start up behavior at any time.Describe alternatives you've considered
The current solution requires either using
SnapTo()
and calculating the goal orientation manually, or setting the Lerp move & rotation time to 0 for a frame. Both work, its just extra overhead.Additional context
Credit to @Alexees for this one. https://stackoverflow.com/questions/59045520/how-to-spawn-solvers-with-initial-orientation