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?
Washed out (double gamma correction) on OpenGL
No matter which swapchain format I specify, my OpenGL application always renders washed out. That implies that OpenGL always thinks it is rendering to a linear render target, while OpenXR always thinks I am submitting an sRGB render target. Changing the swapchain format that I ask OpenXR to create between sRGB and linear makes no difference, and neither does glEnable(GL_FRAMEBUFFER_SRGB).
Android WebView Render Error
I'm making a VR simulation that uses Vuplex's WebView for Android - the canvases are taken from the poke interaction scene, with a WebView added to the Unity Canvas. Most of them load up just fine, but the one webpage I have is popping up an error about render resolution being too high. This seems to be some kind of WebGL problem (since it has a max size of 4096), but sizing down the canvas resolution hasn't stopped this error. We've had this error pop up on our computers as well, but it was fixed by updating Chromium to v115. It seems like the Quest is only on Chromium 91. Is there any way to update this outside of an Oculus update, or are we just kind of screwed until that happens? Does anyone have other suggestions to try?
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 herehelp with oculus rift pc sdk
Hello I have been trying for a week now to write a simple app to display an image on oculus rift ( same for both eyes ). OculusTinyRoom is the only sample using OpenGL and it is way too complicated to adapt. I am reaching the point where I am starting to doubt that this library is maintained any longer. Are there better alternatives? The oculus sdk guide is outdated and almost every sample I can find on the net is at least 3 years old, would not compile against the newest sdk, and using an older sdk would often result in blank screens or all kind of errors. I am using C++ / OpenGL / Visual Studio 2017. Can anyone please help me with a link to an updated sample? Thank you !
