Using the latest public test channel (v63) on a Meta Quest Pro and the Meta Quest Link PC app, I'm no longer able to use the hand tracking (XR_EXT_hand_tracking) and body tracking (XR_FB_body_tracking) extensions over AirLink. They have worked fine in previous versions but the extensions are no longer supported by the runtime. I have all the developer mode settings enabled and ensured hand/body tracking is enabled on the Quest Pro. Face and eye tracking still work properly though. Is there some other setting I need to turn on somewhere to enable these features or is there an issue with the latest version?
I believe I've found what is causing this issue. My application folder contains the file dbghelp.dll. I think this is somehow conflicting with the version that is in Oculus/Support/oculus-runtime folder. If I remove this file from my app directory then the hand tracking, body tracking, and passthrough extensions work again. Copying the same version of the DLL from the Oculus/Support/oculus-runtime folder to my app folder does not fix the issue. So it appears the Oculus runtime does not currently load all extensions properly if the application folder contains dbghelp.dll.
These extensions worked correctly in a previous version of the Oculus OpenXR runtime even with the presence of this DLL in my app folder. Any chance the Oculus runtime can be updated to allow these DLLs to coexist?
I also have issues with dbgeng.dll when I launch my unreal engine project ever since v63, removing the DbgHelp folder gets rid of the error but this wasn't a problem before the update
Getting the error on launch but its isn't stopping me getting in if you just keep pressing ok my concern is on build possibly hitting issue.
This is troublesome and definitely needs a fix and this seems to be the most consistent response so far as I have been working with others to figure out the issue so a dev response would be helpful.
for note talking with some other people. some who work on windows 10 don't seem to have this issue present. HOwever I am on 11 and I can confirm the error popping up for me
I've experienced the issue on multiple Windows 10 machines. It's frustrating to see that this issue was pushed out to the public channel. Is there a better place to report issues with the test channel?
From my experience Meta support will either not reply or tell you to post on the forums and here nobody seems to check for reported issues, this has been going on for a month now for myself and many others ever since v63 was released, there's multiple threads here about it
