We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality. If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers. And always feel free to hit us up on Twitter @MxdRealityDev.
SurfaceObserver's SurfaceChangedDelegate gets odd bounds
I am currently working on a HoloLens Unity project, where i want to scan the structure of some really big rooms via spatial mapping.
Since I don't want all the submeshes generated by the SurfaceObserver to be loaded in memory at the same time, I use some custom caching mechanism based on this article. https://docs.microsoft.com/en-us/windows/mixed-reality/spatial-mapping#mesh-caching
I want to filter out changes of submeshes which are not interesting before bakeing the mesh.
According to the following Unity documentation page I can use the bounds given to the SurfaceChangedDelegate callback to do this.
The center of the bounds doesn't match the center of the baked mesh in global space.
The extends of the bounding boxes are also the same for each mesh part.
Am I missing some transformation or something like that?