Closed bhtruong93 closed 9 months ago
@keveleigh or @davidkline-ms have either of seen this issue? Does this seem like it could be related to this OpenXR issue?
https://github.com/microsoft/OpenXR-Unity-MixedReality-Samples/issues/52
@bhtruong93, have you seen this issue Unity 2019? I believe you've recently upgraded to 2020. Also, are you using the Windows XR Plugin or the Mixed Reality OpenXR Plugin? And what versions?
@AMollis no we haven't seen this in Unity 2019. Yes, you're right we're currently testing on an upgraded 2020 branch. We're also using Mixed Reality OpenXR, version 1.0.3
We're also using Mixed Reality OpenXR, version 1.0.3
Are you able to update to a newer version? The spatial mapping support in Mixed Reality OpenXR was basically rewritten between 1.0.3 and 1.1.0. It would be interesting to see if you're still able to repro after updating to the latest.
@keveleigh thanks for the tip. Verified that the problem still persists in our app as well as the clean test app using Mixed Reality OpenXR 1.3.0 and Unity OpenXR 1.3.1
I am investigating this now. Hope to have some more information for you soon.
@davidkline-ms do you have any thoughts on work arounds? Two specific questions
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
The spatial mesh is shifted when returning to the app after putting the device to seep
To reproduce
Steps to reproduce the behavior:
Expected behavior
The spatial mesh should recover and align itself like it was before putting the device to sleep
Your setup (please complete the following information)
Target platform (please complete the following information)
Additional context
Repo here https://github.com/bhtruong93/spatial-mesh-bug-2.7.3 Essentially it is an empty project with the setup and a scene that uses the default configurations for MRTK