Closed elbuhofantasma closed 9 months ago
This sounds like an issue that might be fixed in 2.6, via PRs like https://github.com/microsoft/MixedRealityToolkit-Unity/pull/8894 from @MaxWang-MS
MRTK 2.6.1 and Unity 2020.3.0f1, 2019.4.22f1, and 2018.4.32f1 with the XR configurations above still produce this issue.
Runtime profile switching was added in MRTK 2.6 but it only supports switching profiles via code and not via editor. This is something that we could implement in the future.
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 bug
When the user switches MRTK profiles while using the in-editor player, input simulation will act in unexpected ways and the Unity Console will generate 999+ camera errors.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Stopping the in-editor player with an appropriate Error message that is generated in the Unity console.
Screenshots
Your setup
Target platform