Forum Discussion
Recent Oculus v63 update generates warnings in Unreal about dbgeng.dll / StackWalk2
Using Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361) we are now seeing repeated warnings when loading an Unreal application (or even just the Unreal Editor). The Unreal application copies a version of dbghelp.dll across to the ThirdParty binaries folder, but this was always the case, and the warnings did not appear before the Oculus update. If the Oculus app is uninstalled, these warnings do not appear. Are any Oculus developers looking into this? Thanks.
Possibly related to https://communityforums.atmeta.com/t5/OpenXR-Development/OpenXR-hand-body-tracking-extensions-not-working-over-AirLink-in/m-p/1155017#M725
23 Replies
Replies have been turned off for this discussion
replied to the link but can confirm the same issue.
Fits the time line of the update for me
I'm running windows 11 if you can confirm the same.
others running windows 10 do not seem to be having the same issueVictor Lerp is looking into it
https://forums.unrealengine.com/t/entry-point-not-found-dbgeng/1775727
In your 'Path' System variable, is the oculus-runtime location specified before or after your windows/System32 entry? I'm not getting this error on Windows 11, my oculus-runtime folder is pathed before the System32.
(I'm just hunting around for possible causes, so this might not be significant)Mine is set before
If this doesn't happen for you on Win11 with Meta Link v63/v64, are you using UE4 or UE5?
UE5.3.2
Meta Quest Link 63.0.0.216.361 (seems to be the version people are reporting an issue with?)
dbgeng.dll and dbghelp.dll are both 10.0.22621.2506 in system32 folder.
The versions in the oculus-runtime folder are,
dbgeng.dll 10.0.17763.1
dbghelp.dll 10.0.17763.132
The error shows up even in an empty non-VR project in UE4, just launching the editor to create a new project causes the error to pop up, and as the OP mentioned uninstalling the Oculus app fixes it
Yep, can now confirm that too.
A workaround for now, rename the DbgHelp folder within the Engine/Binaries/Thirdparty folder for the version of the engine you're trying to work with. (I just added an underscore to the end).
Error is invoked in LibOVRRT64_1.dll I think.
Yeah I tried that but then packaging throws an error, I've dealt with this for a month now so I'll just wait a little longer and hope someone does something about it on the Unreal side
I just don't understand why it's so difficult to communicate those issues to Meta, they don't check their own developer forums, their support team doesn't really care
It's a path issue of some sort for sure, because the log shows UnrealEditor opening the System32 version of the dbgeng.dll (which isn't a full implementation) ->
'UnrealEditor.exe' (Win32): Loaded 'D:\EpicGames\UE_5.2\Engine\Binaries\ThirdParty\OpenXR\win64\openxr_loader.dll'.
'UnrealEditor.exe' (Win32): Loaded 'C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT64_1.dll'.
'UnrealEditor.exe' (Win32): Loaded 'C:\Windows\System32\gpapi.dll'.
'UnrealEditor.exe' (Win32): Loaded 'C:\Program Files\Oculus\Support\oculus-runtime\RuntimeIPCServiceClient_64.dll'.
'UnrealEditor.exe' (Win32): Loaded 'C:\Program Files\Oculus\Support\oculus-runtime\client-plugins\x64\XR_EXT_hand_tracking.dll'.
'UnrealEditor.exe' (Win32): Loaded 'C:\Windows\System32\dbgeng.dll'.
'UnrealEditor.exe' (Win32): Loaded 'C:\Windows\System32\DbgModel.dll'.Could you try copying the 'dbgeng.dll' file from Program Files/Oculus/Support/oculus-runtime into your UnrealEditor.exe folder, e.g. Epic Games/UE_5.2/Engine/Binaries/Win64
See if you are able to package after doing that?
Copying the Oculus dbgeng to UE_4.27\Engine\Binaries\Win64 solves the issue for the editor, but my packaged game still throws the error because of the dbghelp file in Engine\Binaries\ThirdParty\DbgHelp
And renaming the Epic Games\UE_4.27\Engine\Binaries\ThirdParty\DbgHelp folder still prevents me from packaging my project as it fails to copy the dbghelp.dll file to my project folder
A bit of a faff, but another possible workaround. How about installing UE5.3.2, then copying and pasting it's ThirdParty\DbgHelp folder into the engine version you are using? (Backing up/renaming the original version so you can put things back later).
Does that resolve the packaging issue?That works 😄
Hopefully this will not cause any issues as I'm getting ready to package my demo for Steam
Thank you so much for helping out!
Khebab did that package well enough for you ?
