On Quest builds (from Unreal 4.27.2) the hands sometimes don't initialize
Hi, Wondering if anyone has an idea of why (since a firmware update a few months ago) the touch controllers sometimes don't initialize properly on startup. They motion controllers components just track to 0,0,0. The issue can be recovered if the user presses the oculus button and returns to the app, but so far we don't have a software solution to reinitialize them. DR795Views0likes1CommentUnreal game launching Assertion failed: AsyncLoadingThread crash
Hello, After a while of not building my game for Quest 2 Standalone, I am back to get that version ready. I managed to compile the code and to package without failing. But when the game launches to the Quest 2, the game instantly crashes back to the main hub. This is the error I get on the Output Log, which is not much to know what is going on, or who is the culprit. LogPlayLevel: 05-18 09:34:57.699 5979 6009 D UE4 : [2022.05.18-14.34.57:699][ 0]LogInit: Texture streaming: Enabled LogPlayLevel: 05-18 09:34:58.237 5979 6114 D UE4 : [2022.05.18-14.34.58:237][ 0]LogTcpMessaging: Started Connection to '127.0.0.1:56709' LogPlayLevel: 05-18 09:34:58.237 5979 6114 D UE4 : [2022.05.18-14.34.58:237][ 0]LogTcpMessaging: Discovered node '3D9595EF4C50F82740AFF3AED2CEE6B5' on connection '127.0.0.1:56709'... LogPlayLevel: 05-18 09:34:58.439 5979 6009 D UE4 : Assertion failed: AsyncLoadingThread.RecursionNotAllowed.Increment() == 1 [File:D:/Build/++UE4/Sync/Engine/Source/Runtime/CoreUObject/Private/Serialization/AsyncLoading.cpp] [Line: 3992] LogPlayLevel: 05-18 09:34:58.439 5979 6009 D UE4 : LogPlayLevel: 05-18 09:34:58.439 5979 6009 D UE4 : [2022.05.18-14.34.58:439][ 0]Assertion failed: AsyncLoadingThread.RecursionNotAllowed.Increment() == 1 [File:D:/Build/++UE4/Sync/Engine/Source/Runtime/CoreUObject/Private/Serialization/AsyncLoading.cpp] [Line: 3992] LogPlayLevel: 05-18 09:34:58.439 5979 6009 D UE4 : LogPlayLevel: Error: 05-18 09:34:58.439 5979 6009 D UE4 : [2022.05.18-14.34.58:439][ 0]LogAndroid: Error: === Critical error: === LogPlayLevel: Error: 05-18 09:34:58.439 5979 6009 D UE4 : [2022.05.18-14.34.58:439][ 0]LogAndroid: Error: LogPlayLevel: Error: 05-18 09:34:58.440 5979 6009 D UE4 : [2022.05.18-14.34.58:440][ 0]LogAndroid: Error: Assertion failed: AsyncLoadingThread.RecursionNotAllowed.Increment() == 1 [File:D:/Build/++UE4/Sync/Engine/Source/Runtime/CoreUObject/Private/Serialization/AsyncLoading.cpp] [Line: 3992] LogPlayLevel: Error: 05-18 09:34:58.440 5979 6009 D UE4 : [2022.05.18-14.34.58:440][ 0]LogAndroid: Error: LogPlayLevel: Error: 05-18 09:34:58.440 5979 6009 D UE4 : [2022.05.18-14.34.58:440][ 0]LogAndroid: Error: << callstack too long >> LogPlayLevel: Error: 05-18 09:34:58.440 5979 6009 D UE4 : [2022.05.18-14.34.58:440][ 0]LogAndroid: Error: LogPlayLevel: Error: 05-18 09:34:58.440 5979 6009 D UE4 : [2022.05.18-14.34.58:440][ 0]LogAndroid: Error: LogPlayLevel: 05-18 09:34:58.484 5979 6009 D UE4 : [2022.05.18-14.34.58:484][ 0]LogExit: Executing StaticShutdownAfterError LogPlayLevel: 05-18 09:34:58.487 5979 6009 D UE4 : [2022.05.18-14.34.58:487][ 0]LogAndroid: FAndroidMisc::RequestExit(1) LogPlayLevel: Took 0.6029501s to run adb.exe, ExitCode=0 Any ideas on how I could start to look into why my game is crashing? I feel like I have no tools to know what is going on. What I've tried so far is to remove as many maps I can to see if reducing drawcalls, triangles, and texture helps. but no success yet.Solved19KViews0likes4Comments
On Quest builds (from Unreal 4.27.2) the hands sometimes don't initialize
Hi, Wondering if anyone has an idea of why (since a firmware update a few months ago) the touch controllers sometimes don't initialize properly on startup. They motion controllers components just track to 0,0,0. The issue can be recovered if the user presses the oculus button and returns to the app, but so far we don't have a software solution to reinitialize them. DR
