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.
HolographicSpace::SetDirect3D11Device throwing exception
Maybe someone has seen this before...
In the spinning-cube template, I'm seeing this line throw a COM exception:
Looks like the root of the exception is:
analog\common\exclusiveapptransport\lib\holographicpresentationsource.cpp(200)\Windows.Mirage.dll!00007FFAB0A5097A: (caller: 00007FFAB0A4E856) ReturnHr(1) tid(5b5c) 8007000E Not enough storage is available to complete this operation.
... and it bubbles up the call stack until it continues throwing in a loop. Consequently, SetDirect3D11Device never returns and my own exception handling is never triggered.
Windows build 16257, MR drivers 10.0.16265.100, AH100 (Acer headset)
Looks like I've plenty of free RAM, VRAM, and disk space -- not sure which if any resource it's out of.