# Tearing in VR since 570.x

**URL:** <https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594>\
**Category:** Linux\
**Tags:** ubuntu\
**Created:** [March 19, 2025, 12:20pm UTC](https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594 "2025-03-19T12:20:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Corben78](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/corben78/32/12946_2.png) [@Corben78](https://forums.developer.nvidia.com/u/Corben78)\
**Post date:** [March 19, 2025, 12:20pm UTC](https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594/1 "2025-03-19T12:20:14Z")

</div>

Since Linux driver 570 (no matter if .86 or .124) I got tearing in VR with the Valve Index on my nVidia 2080 via Display Port. I’m on Ubuntu 24.04 LTS. It’s independent of if GSP is enabled or not or NVreg\_RegistryDwords=RMIntrLockingMode=1 is present or not.  
I tried both setting it as a grub boot parameter “nvidia.NVreg\_EnableGpuFirmware=1 nvidia.NVreg\_RegistryDwords=RMIntrLockingMode=1” and `sudo update-grub` or via module setting in `/usr/lib/modprobe.d/nvidia.conf` and afterwards using `sudo update-initramfs -u -k all` (but not grub and modprobe at the same time).

Shaking my head in VR reveals a horizontal line where the upper and lower images have different latency. Comparabel to the latancy introduced here: [Latency in VR (with GSync) since 440.44](https://forums.developer.nvidia.com/t/latency-in-vr-with-gsync-since-440-44/119362)

Where this seperation line occurs seems random, once I was in the upper quarter another time in the lower quarter.

It’s independent of if I use SteamVR or Monado, if async reprojection is enabled or not.

Downgrading to driver 565 resolves this issue, just the rendering latency issue (linked above) remains, just no tearing.

I do not have this issue on my PC with 3070 using HTC Vive via HDMI on driver 570.x (disabled GSP though, as the stutter/lags in VR issue is not solved with setting NVreg\_RegistryDwords=RMIntrLockingMode=1)

---

<div class="post-metadata">

**Author:** ![Corben78](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/corben78/32/12946_2.png) [@Corben78](https://forums.developer.nvidia.com/u/Corben78)\
**Post date:** [March 23, 2025, 8:50pm UTC](https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594/2 "2025-03-23T20:50:37Z")

</div>

Looks like the tearing could be OpenVR only. It occurs in Beat Saber 1.29 but not in Pistol Whip, while Beat Saber 1.29 (using legacy beta branch) is not yet OpenXR, Pistol Whip is OpenXR. Needs more testing to narrow it down.

edit: it also happens in Pistol Whip.  
Yet as written in the other thread ([Latency in VR (with GSync) since 440.44 - #8 by Corben78](https://forums.developer.nvidia.com/t/latency-in-vr-with-gsync-since-440-44/119362/8)), the headtrack delay seems gone in Monado with the `U_PACING_COMP_PRESENT_TO_DISPLAY_OFFSET_MS=10`setting.

---

<div class="post-metadata">

**Author:** ![vsTerminus](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/vsterminus/32/354244_2.png) [@vsTerminus](https://forums.developer.nvidia.com/u/vsTerminus)\
**Post date:** [September 24, 2025, 6:24am UTC](https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594/3 "2025-09-24T06:24:02Z")

</div>

This is still affecting me, all the way up to 580.82.09 (on Gentoo), although it seems to be tied to async reprojection for me.

- Independent of refresh rate
- Occurs all the time, in and out of games
- Only occurs when two conditions are met:
  - “enableLinuxVulkanAsync” : true in steamvr.vrsettings
  - steamvr is actually able to enable async reprojection
    - Either by running steam with STEAM\_RUNTIME=1, or by using setcap CAP\_SYS\_NICE=ep on vrcompositor-launcher and launching it outside of steam.

- I haven’t experimented with module parameters yet

Otherwise it’s exactly like Corben78 describes: The lower 1/3? of the view has a curved horizontal tear line where everything below seems to lag behind everything above when I move my head around.

565 (Specifically 565.77 for me) works without issue, but I won’t be able to stay on that version forever. Every driver since then has experienced this horizontal tear issue when async is enabled.

---

<div class="post-metadata">

**Author:** ![vsTerminus](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/vsterminus/32/354244_2.png) [@vsTerminus](https://forums.developer.nvidia.com/u/vsTerminus)\
**Post date:** [December 21, 2025, 6:54pm UTC](https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594/4 "2025-12-21T18:54:22Z")

</div>

Still happening to me as of 580.119.02 on Gentoo

If Steam can enable async reprojection I get a horizontal tear and everything below it has different latency from everything above it. This causes the bottom portion of the screen to “lag behind” as I move my head around.

Here is a bug report log where I booted the computer and logged in, launched Steam with “STEAM\_RUNTIME=1 steam”, and then launched SteamVR. I confirmed that Asyncronous Reprojection was enabled in the logs:

`Sun Dec 21 2025 12:35:09.661729 [Info] - Attempting to enable async support… `  
`Sun Dec 21 2025 12:35:09.661744 [Info] - Enabling async support!`

[nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/psL96DSRVhzY2Ddhq8xKpUumQdf.gz) (1.3 MB)

---

<div class="post-metadata">

**Author:** ![vsTerminus](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/vsterminus/32/354244_2.png) [@vsTerminus](https://forums.developer.nvidia.com/u/vsTerminus)\
**Post date:** [December 21, 2025, 7:18pm UTC](https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594/5 "2025-12-21T19:18:26Z")

</div>

Here’s another, same behavior on 590.48.01

Maybe worth noting, the location of the tear line changes. As I continue to move my head around the line moves lower and then briefly disappears, and when it does it looks like async has been fully disabled. Then it comes back, higher in my viewport again and the behavior repeats.

[nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/li3IQ4jiTWGQjdlbIJXMlTzhjIM.gz) (684.4 KB)

---

<div class="post-metadata">

**Author:** ![joni\_999](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/joni_999/32/246178_2.png) [@joni\_999](https://forums.developer.nvidia.com/u/joni_999)\
**Post date:** [December 30, 2025, 6:48pm UTC](https://forums.developer.nvidia.com/t/tearing-in-vr-since-570-x/327594/6 "2025-12-30T18:48:50Z")

</div>

Sounds somewhat similar to

> [@Enabling GSP makes SteamVR unplayable on RTX 3090ti](https://forums.developer.nvidia.com/t/enabling-gsp-makes-steamvr-unplayable-on-rtx-3090ti/298694):
>
> Hi! I am currently experiencing terrible lag in SteamVR on nvidia driver 555.58.02 with GSP enabled. As soon as I disable it it works flawlessly again. The lag only happens inside the VR headset - the “mirrored” game on the desktop is completely fine. GSP Off: [SteamVR no issues GSP Off] GSP On: [SteamVR shenanigans] The purple lines in the performance graph are frames with “Display Error” Bug report created with GSP On: [nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/bBrNydA2navLrwDyacdow302zEO.gz) (904.2 KB)

and its connected github issue:

> <https://github.com/NVIDIA/open-gpu-kernel-modules/issues/992#issuecomment-3700106556>
>
> \### NVIDIA Open GPU Kernel Modules Version
> 
> 590.48.01
> 
> \### Please confirm this i…ssue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
> 
> \- \[x\] I confirm that this does not happen with the proprietary driver package.
> 
> \### Operating System and Version
> 
> Arch Linux
> 
> \### Kernel Release
> 
> 6.18.2-2-cachyos
> 
> \### Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
> 
> \- \[x\] I am running on a stable kernel release.
> 
> \### Hardware: GPU
> 
> GeForce RTX 3090 Ti
> 
> \### Describe the bug
> 
> If adaptive sync is enabled on any of my connected monitors and I start SteamVR, the VR headset's displays will experience some kind of screen tearing, making it unusable for VR gaming.
> 
> I'm using a Valve Index VR headset.
> 
> In the performance graph it will look like this:
> 
> \<img width="285" height="312" alt="Image" src="https://github.com/user-attachments/assets/ee05d5d7-a6c0-4887-b31b-dd756be819ae" /\>
> 
> 
> Currently the only working configuration is using the proprietary driver and turning off GSP - so it seems to have something to do with GSP.
> What it should look like:
> 
> \<img width="275" height="290" alt="Image" src="https://github.com/user-attachments/assets/a051db15-e15a-46e1-84ef-93aa66d6ef78" /\>
> 
> A working workaround is setting the following in a modprobe.d file:
> \`options nvidia-modeset conceal\_vrr\_caps=1\`
> 
> \### To Reproduce
> 
> 1) Enable adaptive sync in your monitor's settings and optionally turn it on in your desktop environment's settings (the issue also manifests if you have adaptive sync "off" in your desktop environment's settings)
> 2) Start SteamVR 
> 3) Put on your VR headset and observe screen tearing and stuttering in the headset's display
> 
> \### Bug Incidence
> 
> Always
> 
> \### nvidia-bug-report.log.gz
> 
> \[nvidia-bug-report.log.gz\](https://github.com/user-attachments/files/24379688/nvidia-bug-report.log.gz)
> 
> \### More Info
> 
> There is also a forum thread here:
> https://forums.developer.nvidia.com/t/enabling-gsp-makes-steamvr-unplayable-on-rtx-3090ti/298694
> If the issue is wrong here, please inform the respective team on your side and close one of the two tickets.
