OpenGL 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?
In XrCompositor_NativeActivity.c, how to disable rendering of texture samples?
There's no glDrawElements() or glDrawArrays() that renders these three textures. Can someone please help me? XrCompositor_NativeActivity.c is an OpenXR Android Studio Native Development project from the Oculus OpenXR Mobile SDK.Strange vertex-buffer corruption in Unity on Quest using compute shaders + Graphics.DrawProcedural?
So here's a bug that's been plaguing me for the last 18 months. Initially I chalked it up to the Quest being quite new, and just walked away from it as a dev platform expecting it to be fixed eventually. I tried again recently, and this is still a problem! Basically, when drawing more than a few thousand vertices with Graphics.DrawProcedural in a shader that uses SV_VertexID to fetch elements from a StructuredBuffer , things work perfectly fine in standalone builds, but on Quest everything goes crazy. All the vertices end up with bizarre positions, normals, etc, resulting in huge triangles going everywhere. Even stranger, vertices that aren't part of my system, such as the default Avatar hands, also have their vertices corrupted! I've experienced similar problems in the past using Graphics.DrawMeshInstancedIndirect There's no difference if I'm running in OpenGL ES 3.1+AEP, OpenGL ES 3.2, or Vulkan. I've tried messing with all sorts of settings, with no luck. Has anyone had any luck with Compute Shaders + Quest? I have a sneaky suspicion that there's just some difficult-to-find documentation about threadgroup sizes or compute shader features that need to be managed properly for writing Compute Shaders in Unity for Open GL or Vulkan. But I'm also worried that there's just some bug in the integration of the Oculus SDK in Unity. Help? I have a pair of videos, one showing what an earlier version of one of my apps looks like on PC, and the second video showing what the same app looks like through the lens on Quest. Notice both the complete polygonal mess in the background, and the strange spiky vertices on the Avatar hands. You can view the videos in this post on my website. I also made several posts about a related issue with Graphics.DrawMeshInstancedIndirect on the Unity forum over a year ago, which you can view here
Can Oculus Quest support 2 activities
I use UE4 and Native SDK to develop a Quest APP.The logic is that i can see the UE4 activity firstly,then jump to anther activity that is developed by Android Native SDK. The problem is that i cann't see anything in this activity of Native SDK after jumded. But there is no problem in Oculus Go using this APP.
