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.
Emulator freeze
Trev
✭
Has anyone else had a issue with mesh/spatial mapping causing the emulator to freeze up?
I've got a very simple Unity app with a basic floating cube. Added the spatial mapping script (the new/fixed script) with the mesh material assets provided for the Origami project. The mesh is set to be visible.
When deployed to the emulator, my app works great...except now that I've added the mesh (using one of the sample room meshes). The emulator freezes either immediately, or after navigating through the room for a couple of seconds. I can recover by killing the app via the HL web portal.
I'm running on a Surface 3 Pro. Is the mesh just too much for the emulator to process? The GPU jumped up to 75% with the mesh, btw. Thanks!
Best Answer
-
Options
Try building in Release mode, it makes a huge difference in performance.
5
Answers
Has anyone else out there had this problem?
Try building in Release mode, it makes a huge difference in performance.