Metahuman crashes Unreal Engine in VR Preview for Quest 3
Hello, Maybe someone had this problem with metahuman and have found a solution? 1. I have a scene that is working on Quest3 build and also in VR Preview mode. 2. I've downloaded and added metahuman I've created. 3. I've enabled all the necessary plugins and compiled shaders. 4. I've dragged downloaded metahuman blueprint into the scene. 5. I'm running VR Preview and then Unreal Engine crashes* *When i package game for Quest3 and run from device it works. EDIT: I'm using UE 5.3.2 and MetaXR v60 Last log entries [2023.12.29-10.11.28:819][277]LogOnline: OSS: Created online subsystem instance for: :Context_2 [2023.12.29-10.11.28:859][277]LogSlate: New Slate User Created. Platform User Id 8, User Index 8, Is Virtual User: 1 [2023.12.29-10.11.28:862][277]LogSlate: Slate User Registered. User Index 8, Is Virtual User: 1 [2023.12.29-10.11.28:889][277]vr.PixelDensity = "1" [2023.12.29-10.11.28:894][277]PIE: Server logged in [2023.12.29-10.11.28:896][277]PIE: Play in editor total start time 0,422 seconds. [2023.12.29-10.11.28:899][277]LogWindows: WindowsPlatformFeatures enabled [2023.12.29-10.11.28:948][277]LogRenderer: Warning: Resizing VR buffer to 4128 by 2240 [2023.12.29-10.11.28:960][277]LogHMD: Allocating Oculus 4128 x 2240 depth rendertarget swapchain [2023.12.29-10.11.29:011][277]LogWindows: Error: appError called: Assertion failed: !EnumHasAnyFlags(TextureDesc.Flags, ETextureCreateFlags::RenderTargetable | ETextureCreateFlags::ResolveTargetable) [File:D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Texture.cpp] [Line: 529] [2023.12.29-10.11.29:011][277]LogWindows: Windows GetLastError: The operation completed successfully. (0) callstack from crash: UnrealEditor_D3D12RHI UnrealEditor_RenderCore UnrealEditor_RenderCore UnrealEditor_RenderCore UnrealEditor_Renderer UnrealEditor_Renderer UnrealEditor_Renderer UnrealEditor_Renderer UnrealEditor_Core UnrealEditor_Core UnrealEditor_RenderCore UnrealEditor_RenderCore UnrealEditor_Core UnrealEditor_Core kernel32 ntdll I'll try to install debugging symbols for engine and test again
Is it possible to perform AR tracking on images viewed through the passthrough mode of the Quest 3
If I use the passthrough feature of the Meta Quest 3 along with AR Foundation and the Meta XR All-in-One SDK, is it possible to perform image tracking on images viewed through passthrough? As far as I know, this is not possible because the Quest 3's camera lacks image processing capabilities.
v63 - The wireless ADB debugging prompt shows a black screen.
Hi, Two tickets were opened here : https://communityforums.atmeta.com/t5/Get-Help/PTC-v63-The-wireless-debugging-prompt-does-not-appear-and-shows/m-p/1171644 and here https://communityforums.atmeta.com/t5/Get-Help/PTC-v62-The-USB-debugging-prompt-does-not-appear-when-the/m-p/1171979 But I was asked to post this here. To resume : On Q2, Qpro and Q3 (v62, v63) when the authorize WiFi debugging through adb prompt shows up, the Quest will first enter a black screen state. Then, we must click the home button on the right controller to make this window show. If I do not click the home button, it will remain in a black screen state. USB debugging prompt had same problem on v62 but it has been fixed on v63 thank to the new look/UI of the prompt. But the wireless debugging prompt have not been updated and still run into this problem. To fix the problem, Meta developers should update the wireless debugging prompt to the new look/UI.
