Meta Quest 3: Low Memory Error
Hello everyone, I know a lot of people have had this problem but I can't seem to find a solution, it happens to me more often when playing Blade & Sorcery: Nomad but it will just randomly crash saying "Low Memory". Was trying to play it last night but crashed about 3 times within about 5 minutes of each other every time.Known Issue: Closing Steam VR crashes Dash
Hi everyone! We're seeing a small group of Steam VR users finding that Dash is crashing on headset and that their PC is becoming unresponsive once they quit the app. The team is working on identifying and fixing the root cause of this issue, and right now the investigation shows that this is likely related to Hardware Accelerated GPU Scheduling being enabled when using certain Nvidia GPUs. If you're having this issue, there is a workaround In the meantime! You can prevent this happening by disabling the Hardware Accelerated GPU Scheduling feature. To do so, follow these instructions. If you need any further help or have noticed other bugs around Steam VR, please comment below. Let me know if you have any questions!
Assertion Failed !bWasCanceled at AsyncLoading.cpp
Hello! Im starting to prepare my game for VR and using the launch option on quest 2 throws me this error line, crashing the game back to Meta lobby. Does anyone know what is happening here? or how I can track it better? LogAndroid: Error: === Critical error: === LogAndroid: Error: LogAndroid: Error: Assertion failed: !bWasCanceled [File:./Runtime/CoreUObject/Private/Serialization/AsyncLoading.cpp] [Line: 1517] LogAndroid: Error: LogAndroid: Error: [Callstack] 0x0000007169AE178C libUnreal.so(0x000000001243B78C)!FPrecacheCallbackHandler::RequestComplete(bool, IAsyncReadRequest*) [] LogAndroid: Error: [Callstack] 0x000000716934875C libUnreal.so(0x0000000011CA275C)!FGenericReadRequest::PerformRequest() [] LogAndroid: Error: [Callstack] 0x000000716563A3A4 libUnreal.so(0x000000000DF943A4)!FAsyncTaskBase::DoWork() [] LogAndroid: Error: [Callstack] 0x000000716563C7B0 libUnreal.so(0x000000000DF967B0)!FAsyncTaskBase::DoThreadedWork() [] LogAndroid: Error: [Callstack] 0x0000007169420718 libUnreal.so(0x0000000011D7A718)!FQueuedThread::Run() [] LogAndroid: Error: [Callstack] 0x0000007169416CB8 libUnreal.so(0x0000000011D70CB8)!FRunnableThreadPThread::Run() [] LogAndroid: Error: [Callstack] 0x000000716927E6D4 libUnreal.so(0x0000000011BD86D4)!FRunnableThreadPThread::_ThreadProc(void*) [] LogAndroid: Error: [Callstack] 0x000000728BEFA1DC libc.so(0x00000000000DF1DC)![Unknown]() [] LogAndroid: Error: [Callstack] 0x000000728BEA62F0 libc.so(0x000000000008B2F0)![Unknown]() [] Thanks for your assistance!
UE4.27 VR Preview crash when 'play as client'
Hi, I'm developing multiplayer FPS Game and trying to use spacewarp on UE4. I followed Oculus guide here : https://developer.oculus.com/documentation/unreal/unreal-asw But when I set 2 players and try to Play VR preview with 'Play as Client' setting in editor, editor just shut down without any crash report. (It works on 'Play as Standalone') It also occur on VR template project.. Does anyone know solution? Thanks for your help. Here is my UE4 version in use. Project version : ue4-oculus-4.27.2-1.70.0-v38.0 ps. I found log output from saved log file [2022.04.25-03.05.23:204][452]LogWindows: Error: === Critical error: === [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:204][452]LogWindows: Error: Fatal error: [File:C:/UE4oculus427/Engine/Source/Runtime/RenderCore/Private/RenderingThread.cpp] [Line: 902] [2022.04.25-03.05.23:204][452]LogWindows: Error: Rendering thread exception: [2022.04.25-03.05.23:204][452]LogWindows: Error: Assertion failed: IsValid() [File:C:\UE4oculus427\Engine\Source\Runtime\Core\Public\Templates/SharedPointer.h] [Line: 890] [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:204][452]LogWindows: Error: [Callstack] 0x00007ff9e3d54f69 KERNELBASE.dll!UnknownFunction [] [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:204][452]LogWindows: Error: [2022.04.25-03.05.23:258][452]LogExit: Executing StaticShutdownAfterError [2022.04.25-03.05.23:263][452]LogWindows: FPlatformMisc::RequestExit(1) [2022.04.25-03.05.23:263][452]LogWindows: FPlatformMisc::RequestExitWithStatus(1, 3) [2022.04.25-03.05.23:263][452]LogCore: Engine exit requested (reason: Win RequestExit) [2022.04.25-03.05.23:290][452]Log file closed, 04/25/22 12:05:23OpenGL crashes on Unity 2022.3
I have an application that crashes on start (Unity 2022.3) when built using OpenGL graphics API, switching to Vulkan stops the crashes, but we cannot switch due to requirements. I have narrowed it down to the OVRHandPrefab. If I remove the use of prefab from my rig, the crashes on start stop happening as well (in OpenGL). I am attaching a picture of the Android Logcat crash. Any ideas or solutions?
UE4 crash when using VR Preview since last Oculus app update
Hello, this has been impossible to use the VR preview anymore since the last Oculus app update. Every time you use the VR preview for a second time, Unreal will crash. Please fix this asap, it's making debugging in VR a nightmare. The issue is on 4.27 but I already discussed with several persons having the issue on different versions of UE5.
Unreal 5.2 android build freezing at inconsistent times on Quest 3
I'm currently working on a android project of which I'm building to the Quest 3. Im running into an issue where at inconsistent times the game freezes the current perspective, and I'm able to look behind me to see an upside down version of the frozen view. After this point the only way to leave the game is by force quitting from the Quest menu. I haven't found any other posts talking about this particular crash with the reversed view and was wondering if anyone had encountered this before or has any tips on solving the cause. Thanks in advance!
Oculus Link crashes when Unity enters PlayMode and does not work until Unity Editor is restarted
As described in the discussion title. More often than not does Oculus Link crash out of existence when entering Unity´s play mode. The setup is as follows. I use an official Oculus USB-C cable to connect my Oculus Quest to my Windows10 PC while using any Unity version past 2019 (prev. versions not tested) with the Unity build in XR Oculus package (not the Oculus Integration from the AssetStore). The idea now is that when I press Play in the Unity editor I will be able to test my app in a similar way as if it was installed on the Quest directly. This worked without any issues until some recent Oculus update (can´t tell when exactly) which apparently let´s the Oculus Link app crash very often regardless of Unity Version or complexity of the scene. The Quest itself gets thrown back into the standard Quest homescreen, Unity will just be stuck on a black screen and the Oculus app will restart anew after its disappearance. That by itself is annoying enough. But the main problem is that I cannot just exit Unity play mode, reestablish the Oculus Link and enter play mode again to fix the problem. Oh no! The major time consuming part of this misbehavior is that once it crashed I need to close the Unity editor, then restart Oculus Link, then start the Unity editor again. Imagine having a semi-big project with an active collaborate service checking for changes every time Oculus Link decides to crash and forcing you to restart the editor. Please help. I do not know how to solve this. If someone at least knows a workaround or fix that does spare me from restarting the editor, I´d be more than happy.
