Corner of Meta Quest 3 shows strange colors when in VR preview mode
Upper right corner. It's quite noticeable with the headset on because the edges of my vision become multicolored. This started happening this morning. I'm really not sure why. This only happens in VR preview mode in UE5. I tried it with a sample starter project from oculus-samples github as well, and the same thing happened except the corner was black instead of multi-colored. I don't notice anything when the headset is in standalone mode. I've tried just looking for a messed up corner in Passthrough/First Hand demo/etc, and there's nothing wrong as far as I can tell. Is this something wrong with Quest Link? I've tried it with a different cable and a different port on the computer as well.
What are the differences between Oculus OpenXR and Epic OpenXR ?
There are two option for OpenXR API in UE's Project Settings. One is Oculus OpenXR and another one is Epic OpenXR. I use VRE plugin and if I use Oculus OpenXR, I completely lose hand tracking functionality provided by VRE (which is amazing btw). If I use Epic OpenXR, I get everything I can wish for, except for some reason game's colors are washed out and who knows what else I miss out on (whatever special sauce Oculus OpenXR has over Epic's OpenXR). So, I am wondering what do I lose by going with Epic OpenXR over Oculus OpenXR ?
Android SDK 12l causing crashing for development builds
Recently I've been trying to update my project's android api from 29 to 32, so it can comply with the new requirements for Quest 2. After the update attempting to launch a non-distribution build causes the following crash during the initial splash screen: Initially I thought this was down to lack of permissions. MANAGE_EXTERNAL_STORAGE was added in api 30 without which access to $Storage/obb, where non-distribution obbs are stored on device, would have been denied. However adding this to the extra permissions and ensuring it has been requested on game start has not fixed the issue. Below are the android packaging settings. I also tried editing the automation script to have the obbs appear in the $storage/android/obb folder, while this did fix the initial crashing it lead to other side effects (such as no logs being recorded and instability) & ultimately feels like a step in the wrong direction. Has there been anyone else run into this issue? If so did you find a solution? Any suggestions or troubleshooting thoughts would be deeply appreciated.
