OpenXR tools for windows

[Tomcat388th]

I have a HP G2 and a QUEST 2. I was messing around with the Quest 2 and changed to the runtime to the oculus went to change it back through the OpenXR tools and set it back to the window runtimes I get this error

C;\windows\system32\mixedrealityruntime.json

XRrusult failure [XR_error_runtime_failure.

I had to reinstall windows to fix the windows open xr tools with the windows runtime. 

Anyone know of a fix for this

thanks J

[mbucchia]

Most common cause for this is you have an OpenXR API layer such as OpenKneeboard, XRNS or OXRMC that is installed outside of your ProgramFiles folder.

Check your registry at HKLM\Software\Khronos\OpenXR\1\ApiLayers\Implicit. There shouldn't be any key pointing to a file outside of ProgramFiles.

Delete any offending key to resolve the issue.

[Tomcat388th]

Thank you that fixed it for me.  When you stated that I had a API layer installed outside of my programs folder. I had open kneeboard installed on a different drive. If I install it in c:\programfiles should everything work or does open kneeboard mess up the opxr registry again.

Thanks again 

J

[mbucchia]

22 minutes ago, Tomcat388th said:

Thank you that fixed it for me.  When you stated that I had a API layer installed outside of my programs folder. I had open kneeboard installed on a different drive. If I install it in c:\programfiles should everything work or does open kneeboard mess up the opxr registry again.

Thanks again 

J

I can't remember exactly what OpenKneeboard did, but I thought the latest version took extra care to not break OpenXR Tools. Better is to ask Fred on the OpenKneeboard Discord. 

[Tomcat388th]

I'll check with fred

Thank you again 

J

[actually_fred]

> Check your registry at HKLM\Software\Khronos\OpenXR\1\ApiLayers\Implicit. There shouldn't be any key pointing to a file outside of ProgramFiles.

I disagree with this - it is perfectly valid for them to be anywhere. The problem is that OpenXR Tools for WMR is sandboxed, which means its not compatible with all valid OpenXR API layers. As such, it is not suitable for use as a debugging/testing tool - use OpenXR Explorer instead.

That said, it will be compatible with the next version of OpenKneeboard, however...

> I can't remember exactly what OpenKneeboard did, but I thought the latest version took extra care to not break OpenXR Tools.

The current betas (and the next stable release) will coincidentally fix this - they install to program files instead, but this is primarily because of Microsoft changing the restrictions on registry access for MSIX "full trust" apps; Windows updates removed the ability to reliably write to the registry. I needed to move away from MSIX, so MSI + Program Files + HKLM made sense. A past alpha changed the ACLs on ProgramData\OpenKneeboard to allow access to sandboxed apps; I removed that as the MSIX changes happened shortly after.

OpenXR Tools for WMR are not compatible with current stable releases of OpenKneeboard; this is ignorable, and a bug/shortcoming/oversight in OpenXR Tools for WMR.

> Check your registry at HKLM\Software\Khronos\OpenXR\1\ApiLayers\Implicit. There shouldn't be any key pointing to a file outside of ProgramFiles.

You also need to check HKCU; current stable releases of OpenKneeboard should be there instead of HKLM

Edited January 5, 2023 by actually_fred

[mbucchia]

13 minutes ago, actually_fred said:

I disagree with this - it is perfectly valid for them to be anywhere. The problem is that OpenXR Tools for WMR is sandboxed, which means its not compatible with all valid OpenXR API layers. As such, it is not suitable for use as a debugging/testing tool - use OpenXR Explorer instead.

Yes, to be clear this is a deficiency of OpenXR Tools for WMR, not OpenKneeboard. But it is what it is today. I've been encouraging people to use OpenXR Explorer as well.