Closed RogPodge closed 9 months ago
Something addressed by MRTK v3/vNext's commitment to separating out visual code from underlying states. Will leave open until the next major MRTK release is public.
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 visithttps://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!
Describe the problem
Currently there is a tight coupling between cursors and pointers, making it difficult to manage the state of the cursor in the scene. We should have cursors be separate entities which listen for events from pointers in order to render the correct state.