Forum Discussion
Black lines and flashing screen
While working on a new update for our game Wands, we stumbled upon this new bug on Quest where the screen flickers and black lines appear on screen. I would share a video but apparently I can't post l...
Hi there.
We're on Unreal developing a multiplayer game for Quest and while I can't say I've observed the screen flicker with black lines, we have seen our share of rendering artifacts and odd crashes in our render thread.
From your log, it looks like your application terminates pretty early on around line 115:
06-13 17:46:16.813 1072 1508 I WindowManager: WIN DEATH: Window{b89844c u0 com.CortopiaStudios.Wands/com.unity3d.player.UnityPlayerActivity}
Some general thoughts from my previous debugging on Quest of our application:
- Being on Unity 2017, I'm assuming you're on the OpenGL driver as opposed to Vulkan. Prior to Quest OS v17, we generally saw more rendering problems with Vulkan that forced us to switch back to OpenGL shortly before a milestone. Since v17 we've been on Vulkan without issue.
- Are there any Quest optimizations that you can disable? I frequently disable FFR as a first step to narrowing down rendering bugs.
- Can you connect RenderDoc to your application when the problem occurs? I'm curious if the game is submitting bad render data or if there is a deeper issue at the OS or hardware level.
- If your game uses Oculus multiplayer functionality, what is your send rate like? I was observing random crashes (sometimes originating in the render thread) when trying to push a bunch of data through a rate-limited connection (I used my cell phone as a wifi hotspot to mimic low bandwidth/high latency).
Best of luck! I wouldn't mind taking another look if you have any more information to share.
We're on Unreal developing a multiplayer game for Quest and while I can't say I've observed the screen flicker with black lines, we have seen our share of rendering artifacts and odd crashes in our render thread.
From your log, it looks like your application terminates pretty early on around line 115:
06-13 17:46:16.813 1072 1508 I WindowManager: WIN DEATH: Window{b89844c u0 com.CortopiaStudios.Wands/com.unity3d.player.UnityPlayerActivity}
Some general thoughts from my previous debugging on Quest of our application:
- Being on Unity 2017, I'm assuming you're on the OpenGL driver as opposed to Vulkan. Prior to Quest OS v17, we generally saw more rendering problems with Vulkan that forced us to switch back to OpenGL shortly before a milestone. Since v17 we've been on Vulkan without issue.
- Are there any Quest optimizations that you can disable? I frequently disable FFR as a first step to narrowing down rendering bugs.
- Can you connect RenderDoc to your application when the problem occurs? I'm curious if the game is submitting bad render data or if there is a deeper issue at the OS or hardware level.
- If your game uses Oculus multiplayer functionality, what is your send rate like? I was observing random crashes (sometimes originating in the render thread) when trying to push a bunch of data through a rate-limited connection (I used my cell phone as a wifi hotspot to mimic low bandwidth/high latency).
Best of luck! I wouldn't mind taking another look if you have any more information to share.