Meta's handling of xrCreateVulkanInstance requests duplicate extensions, causing crashes
Trying to execute a VR game with Vulkan when OpenXR runtime is set to Meta causes crashes before the application starts, although not always. I have checked with an empty Unity project that it only happens with Vulkan and Meta runtime environment. After much searching, it led me to this thread on the Unity forums from late 2023, early 2024, where someone from the support team clarifies that it is a problem on Meta's part, and they make that clear in this bug report. It's been over a year since this bug was reported to Meta by Unity itself and it still hasn't been fixed, we're unable to progress in the development of our game because of this bug. We need a fix for this critical bug ASAP.137Views3likes0CommentsUnity ASW URP Fork doesn't work with RenderTextures / Lit Shader
I'm using the Meta URP fork for ASW support (Unity 2022.3). I also have functionality in my game for taking an instant photo onto a RenderTexture. However when I do this the images I get seem to be showing the motion vectors and nothing else. Its definitely due to the fork as identical setup (Vulkan / Standalone build) worked perfectly before the switch over. PCVR / DX11 works fine either way. Is there any way to strip the motion data out of these or a way to force that particular camera to not do the motion vector pass? Also reported here with images: https://github.com/Oculus-VR/Unity-Graphics/issues/34 Sorry for repeat convo (put in the wrong board to start with)421Views0likes0Comments