Maybe someone has seen this before...
In the spinning-cube template, I'm seeing this line throw a COM exception:
m_holographicSpace->SetDirect3D11Device(m_d3dInteropDevice);
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.