The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
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.
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, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Recently I discovered that one of my spaces was corrupted (it was tagged with a red "Corrupted") and the Lens automatically created a new space and started scanning the room from a fresh file. I can no longer load the corrupted space, only option highlighted is to remove it, but I do however have a saved copy of the space on my computer. Is there any way to load that file from my computer to the Lens to somehow fix or overwrite the corrupted space, or will I just have to scan the room again? Also I'm not sure if this is an issue but the space reached about 360mb. Could increasing the size of the space cause problems?
Another somewhat related question of mine: What's the point of dragging the spatial mapping object into the object surface observer script in the spatial mapping prefab when the Lens just loads the spatial mesh from memory? Or does it take this spatial mapping object and use that instead of the one from memory?