search

microsoft / MixedRealityToolkit-Unity

This repository is for the legacy Mixed Reality Toolkit (MRTK) v2. For the latest version of the MRTK please visit https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity
https://aka.ms/mrtkdocs
MIT License
6k stars 2.12k forks source link

Spatial mesh observer stops stops generating meshes at distance from the origin #9623

Closed Connor-Kerwin closed 9 months ago

Connor-Kerwin commented 3 years ago

Describe the bug

XR SDK Windows Mixed Reality Spatial Mesh Observer seems to have inconsistent behaviour when moving away from the origin. I can walk 10 metres away and it stops generating any mesh, but I'm not having any errors thrown, it just seems to stop creating. I've attached a screenshot of the observer profile below. I've also set the MRTK target scale to World scale, if this helps.

Screenshots

image

Your setup (please complete the following information)

Target platform (please complete the following information)

Connor-Kerwin commented 3 years ago

After some investigation, local packaging and instrumenting the mesh creation process, it seems like MRTK is not actually receiving MeshInfo data from the XRMeshSubsystem after a while.

I observed the mesh info list growing to a point, around 60 or 70 meshes, at which point it stopped providing them. The number of generated meshes in the scene matched the number of items in the mesh info list, but the meshes covered a significantly smaller region than where I moved with the device. The bounding volume provided to the mesh subsystem also seemed to be valid.

Looking below at the image comparison, the mesh that generates in Unity and the HoloLens spatial mesh through the device portal differ significantly. Could this be a bug within the mesh provider?

image

holomatt commented 3 years ago

I am also experiencing this issue where the mesh observer is always stationary, regardless of the "is stationary observer" setting.

The meshing data is getting created, but is not loaded in beyond the mesh extents vector3 range. When running in HAR, I can validate this by running and meshing beyond the observer extent value -> stopping and upping the observer extent value -> when pressing play I see the additional mesh data.

Unity 2020.3.12f1, MRTK 2.7.2, WindowsXR Plugin 4.5.0.

Would love to have non-stationary mesh observers again as these rock!

keveleigh commented 3 years ago

We identified this as an issue in Windows XR Plugin. A fix has been merged and is pending Unity's next package release. I'll update this thread when it goes live!

stale[bot] commented 2 years 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.

IssueSyncBot commented 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 visithttps://www.mixedrealitytoolkit.org.

Thank you for your continued support of the Mixed Reality Toolkit!