Skip to main content
sumsar158
Participant
March 24, 2026
Question

Screen tearing lines after v2.1 on quest2 and 3s

Specific Symptoms & Conditions

Only Affects UI/Overlays: The tearing and artifacts only appear on the Quest UI, menus, overlays, and video streaming layers (such as Virtual Desktop or screens with white backgrounds).

3D Environments are Unaffected: Full 3D environments, background environments, and in-game visuals work perfectly fine, as long as no system overlay is present.

Tied to Head Tracking: The visual tearing is triggered by head movement. It appears as horizontal lines when moving the head up and down, and vertical lines when moving the head left and right.

Affected Devices & Firmware

Hardware: The issue is widespread and not isolated to one headset. Users have confirmed this is happening on the Quest 2, Quest 3, Quest 3S.

Software: Multiple users pinpointed that the issue began very recently, specifically after the Horizon 2.1 update.

Troubleshooting Attempted (No Fix Found)

Users have attempted standard fixes, including factory resets and using the Meta Quest Update Tool, but the issue persists.

Hardware defect ruled out: While one user suggested it could be a loose display cable, the community consensus strongly confirms this is a software/firmware issue. A broken display cable would cause persistent visual glitches across all games and apps, whereas this issue dynamically turns on and off depending strictly on whether a UI overlay is present.

 

https://www.reddit.com/r/OculusQuest/comments/1rz62f9/comment/oc5a99g/ - pictures and video included

https://www.reddit.com/r/OculusQuest/comments/1rq1z31/quest_2_rainbowartifacts_tearing_but_only_on_ui/

Possibly: Screen Tearing Artifacts | Meta Community Forums - 1369036

 

 

61 replies

steve40
Honored Contributor
March 24, 2026

I'm on v2.1 and not having this problem.

Meta Engineers are unlikely to follow the community forums. Report the problem in QUICK SETTINGS>REPORT PROBLEM.

And please don't double-post (community rules).

Choleni
Honored Contributor
March 24, 2026

sumsar158​ 

I'm also on v2.1, but I don't have that....I tried it on Quest 3 and Quest 2.

Like steve_40​ said.... report the bug and include your screenshots.

Honored Contributor
March 24, 2026

sumsar158 I have the Quest 3s on V2.1 and I have no issues with screen tearing. 4 other friends in a small local group here don't have it either. It could be a problem with the device or a faulty software update on your headset. If it was a general bug, we would all have it. Follow the suggestions of steve_40 and Choleni and report the bug, through the system so Meta engineers can see it. 

sumsar158
sumsar158Author
Participant
March 24, 2026

and like 8 people have confirmed having this exact issue on the linked posts

Honored Contributor
March 24, 2026

8 people should then report their issues through the bug reporting system. There are millions of Quest 2, 3, and 3s users without the problem. This is why your first step should be a bug report so the Meta software people can either send a fix to your specific device or advise on headset repair or replacement, if there is a more serious issue. 

Participant
March 24, 2026

dude this issue has been driving me crazy. i recently took out my headset after a long time of no use, updated everything, and this occured. i had no idea this came from v2.1. no matter what i googled i couldn't find this issue, i thought it was a hardware issue. 

Honored Contributor
March 24, 2026

cook1e0 It might still be a hardware issue.. Most people don't have the problem, I don't and the group of people I play with don't either.. Only around 8 people according to the OP has reported it. Out of millions of headsets with v2.1 that isn't many. It's not a wide ranging bug. If it was thousands of people would be complaining. As stated in other comments, you should report the problem through the headset bug report system and they can discover if you need an additional update or possibly a hardware issue. As so few people are reporting it, I'm thinking it might be hardware but that's not certain. Hopefully it's just a glitched software update. 🤞

Participant
March 25, 2026

a 'faulty update' doesn't magically create a highly specific rendering bug that only affects 2D UI overlays while leaving full 3D environments completely intact. that's a compositor issue in the code, not a broken download. people are already submitting bug reports, but denying the issue exists just because you and your 4 friends didn't trigger the bug doesn't help anyone.

New Participant
March 25, 2026

Same issue appeared for me after 2.1 update. It really annoying and not allowing to use virtual desktop, 4XVR Video Player, etc. When moving head this annoying stripes showing and it totally ruins experience.

Participant
March 26, 2026

No sé si esta relacionado: estoy en el mismo problema, pero, he observado que VD renderiza ambas caras de la pantalla en passtrough, no recuerdo que lo hiciera antes. Los artefactos me recuerdan a la colision entra las dos caras renderizadas de un poligono, en este caso perteneciente al plano de la pantalla. Curiosidad sin mas? tal vez.

Participant
March 26, 2026

My god.. I'm not the only one...

I’m having the exact same problem on my Meta Quest Pro! I only see this issue in the 2D UI, just like you described. Interestingly, I found a VERY FUNNY symptom: if I launch the web browser first, everything starts working perfectly—like magic!  😀

Check if this issue persists while the web browser is running

Participant
March 26, 2026

Los menús nativos de quest 3 tampoco son fluidos en el scroll. Parecen algún tipo de reproyeccion que, por supuesto, está desactivada en experimental.

Participant
March 26, 2026

I’m experiencing the same issue as well, using a Quest 3. The problem also appears during PCVR. The issue is present in both the 2.1 and 2.3 updates as well. This whole Meta support situation is starting to become quite frustrating…

Participant
March 26, 2026

I don't know if this is related: I'm having the same problem, but I've noticed that VD renders both sides of the screen in passthrough, which I don't recall it doing before. The artifacts remind me of a collision between the two rendered faces of a polygon, in this case belonging to the screen plane. Just curious? Perhaps.