OH MY GOD!!
TL;DR:
Black grid/tearing artifacts appear when moving head in Quest 2 UI and Virtual Desktop after v2.1 update.
Issue does NOT occur in SteamVR (PCVR), only in Quest-native rendering pipeline.
More visible in left eye and UI overlays.
This strongly suggests a problem with Quest compositor / rendering pipeline / frame timing, not GPU rendering itself.
Steps to reproduce:
1. Boot Quest 2
2. Open Virtual Desktop (no need to connect to PC)
3. Move head left/right - black grid lines appear, especially on UI Elements.
- Issue is noticeably stronger in the left eye than the right.
- Right after boot, when all serivces is still loading and the headset is a bit slow, the issue is preset there for a couple seconds before it's gone.
- Opening overlays (e.g. virtual keyboard) significantly increases the issue.
Additional observation:
- The issue intensity depends on head movement speed. Slow movement results in minimal artifacts, while fast head movements significantly increases the visibility of grid lines and distortion.
- The issue is not visible in recordings or screenshots taken from the headset, which suggests it occurs after frame rendering, during final display composition.
- The issue becomes significantly worse when multiple UI layers are present (e.g. virtual keyboard + desktop + overlayes).
Full Story:
I'm a having the same issue! and I though that's because I've messed with my adb commands.
Basically what happened for me is I have developer options unlocked.
I started using Virtual Desktop to boost my PCVR Experience.
With that i use snapdragon super resolution from VD
To boost my headset performance I've raised with SideQuest help my GPU and CPU to Level 4 and lowered my quest texture resolution to Quest 1 size.
Then update 2.1 came out.... and i decided to install without reverting to default settings.
What happened is my quest got permanently stuck in Quest 1 Texture Resolution. Everything pixelated and choppy (the lines when you move your head weren't there yet) .
So my hell began.
I went through countless adb commands, then 5-10 factory resets from USB Updater (hold volume down + power), true recovery menu (hold volume up + power then when the robot appears press volume up and power, and finnally from metas own website i did factory reset).
I was debugging and trying commands for 3 days, reflashed my firmware with meta software tool, adb sideload with both recoveries, cleared whole window compositor (adb shell wm reset) and FINALLY MANAGED to fix the texture resolution...
and then this happened. Now that the resolution is back to normal and quest 2 should be working normally.
I have those black lines when i move my head.
They are mostly preset when you run Virtual Desktop (doesn't even need to connect to PC)
When you move your head around, I've noticed they are more present on left eye than the right one, but if you connect to PC and use desktop mode normally, and put more things on screen, like virtual keyboard for example, those line appear way more on left and right eye.
They seems to almost not exist on home screen unless you first boot your quest and its still laggy from loading things - then you see those lines and artifacts like this.
Now if you go to horizon central, there is this big video screen. When nothing is loaded there, and you move your head, those black grid lines are present there too.
If you open the menu if your left controller, those lines are on whole ui of the window you just opened but instead of them being black, they become transparent and show what is under the window as well as they appear on the borders of windows too.
When you go to horizon worlds and are in the view with the city that is in front of you with the mirror on your right and white window with worlds to pick up from that is in front of you, when you move your head the black grid lines are on the whole windows as well as on the mirror.
When you open vrchat natively on quest 2, things gets different here. Most of the game runs fine but when you are loading to worlds and you see the picture of the world you're about to load into and you move your head. Around that picture transparent lines messes up the image. It looks like graphical artifacts but it's the same thing.
I tried recording this on video with my quest but it seems like the video didn't pick this up so it looks to be a problem with render pipeline and something misaligned and not being able to catch up when you move your head before the image is displayed on your screen.
This is definitely NOT a hardware issue, it's pure software/firmware problem (after my debugging this issue for another 4 days, I've spend on this stuff 7 days straight thinking i messed something up but now I've found this topic and looks like Meta is the ones who messed up theirs's firmware...
Now if you connect your Quest 2 with VD to your PC, run VRChat from there
SteamVR opens up and the problem is gone in steamvr. You can play all your PCVR games in steam VR (I'm using VDXR runtime) without any glitches, artefacts or those gridlines, but as soon as you hold the left controller menu button to open up the Virtual Desktop menu UI where you can see your desktop the black lines are back, if you from there go to desktop mode - the black lines are there when you move your head. Now go back to VR Mode - everything is fine again, so the problem doesn't exist when you view your screen through SteamVR but exists everywhere else when quests rendering is involved.
Worse problem is, I cannot screenshot this so I'm hoping this post will be seen by meta firmware developers or maybe I should just open a support ticket on PC. (reporting this through quest i think is not possible for me.)
Or where should I go to fill a bug report?
Hardware:
Quest 2
Firmware version after which the problem started to occur: earliest v2.1 build that has been distributed to quest 2 now i can't tell the exact build number because since then, Meta release one more firmware update (and it made things even worse).
This problem is present after every type of Factory Reset (even couple times) and even after as I said above flashing my firmware again with different methods.
This issue seems to affect multiple users after the update.
Please investigate Quest compositor / UI rendering pipeline.
