HORRIBLE Screen Tearing on New GPU

[Shield of Ultramar]

Hello! I recently managed to finally snag an RTX 4090 after months of online battle royals vs bots to get one first, installed it, and jumped on Destiny only to find some of the WORST screen tearing I have ever seen. We're talking impacting gameplay levels of bad.

Naturally I went through the usual options, framelock, VSync, Windows Fullscreen, driver updates, the whole nine yards, but nothing seems to fix it. My seven year old GTX Titan X never once had the problem, even running with all settings on max, so I'm a bit perplexed by this. I don't seem to be having the issue in another games either, except for Halo Infinite but just turning on VSync fixed that. I'd appreciate any help or advice anyone may have, as screen tearing is something I've quite literally never had to deal with before.

[senrign]

Damn wish i had problems like this in my life

[Dani3009]

Screen Tearing has nothing to do with the game ...
Also: when you use V-Sync you cannot have Screen Tearing
It's simply not possible

With a 4090 I guess you also have a G-Sync Monitor, so why dont you use that? Make sure to use the nvidia control pannel for that

[Mandarin |Sky|]

Cap your framerate in the Nvidia control panel. Manage 3D settings > Program settings tab > Destiny 2 > Max frame rate. Set it to a couple fps below your refresh rate.

[Shield of Ultramar]

Originally posted by Dani3009:

Screen Tearing has nothing to do with the game ...
Also: when you use V-Sync you cannot have Screen Tearing
It's simply not possible

With a 4090 I guess you also have a G-Sync Monitor, so why dont you use that? Make sure to use the nvidia control pannel for that

That's factually incorrect, mate.

You can still have screen tearing with VSync enabled. In fact, Destiny is notorious for VSync not working. Some people have found that turning the game to Windowed Fullscreen can help, but it's not a guarantee. And yes, G-Sync is already enabled.

[Shield of Ultramar]

Originally posted by Mandarin |Sky|:

Cap your framerate in the Nvidia control panel. Manage 3D settings > Program settings tab > Destiny 2 > Max frame rate. Set it to a couple fps below your refresh rate.

Sadly, that ain't working for me. I did find that turning off DSR has alleviated it a bit, but it's still there to an extent.

[Nuclear_Caliber]

Originally posted by Deus Volk:

Originally posted by Mandarin |Sky|:

Cap your framerate in the Nvidia control panel. Manage 3D settings > Program settings tab > Destiny 2 > Max frame rate. Set it to a couple fps below your refresh rate.

Sadly, that ain't working for me. I did find that turning off DSR has alleviated it a bit, but it's still there to an extent.

I haven't tried the game since the new update. I was going to post a thread about whether or not the screen tearing is fixed. I've tried everything; VSync in game, VSync NVIDIA Control Panel, setting a frame cap, and nothing works. I'm about ready to boot it up to see if there is a change.

[Verios44]

You said its a new GPU. Have you ran DDU by chance during the install?

[DirtyMacho]

Can you post your system spec including monitor and RAM and if oc'ed mention the same.

40-series at times not working well.

Also post the settings -Video snap

Stuttering and screen tearning could be caused due many issue drivers bug/ gpu hardware / PSU


While sharing these. Set the frame rate to 60 and give it a try. IF that goes away then increase by 15 and see when did you see the screen tearing.

Try also swapping the cable to monitor. Usually hdmi might not support this speed unless its 2.1 so you might have hooked up display cable. change port and cable if feasible

[Rimertis]

Go to yout NVIDIA 3D Configuragion "Application settings"and turn V-Sync on for Destiny application. I had the same issue after upgrading to windows 11.

[LaeLena]

For me every instance of screen tearing in this game has been because of graphics drivers. So I've either had to update them or go back to previous version to fix it.

[Fistador]

Thank you Rimertis!! That fixed it for me. Had the same issues as the thread creator