I don’t understand, when I cap my frame rate at 60 and turn off vsync I get screen tearing, but when I turn on vsync I have no issues at all… like what drugs are you on monitor?
I don’t want to use vsync… any tips on how to fix screen tearing, even if I cap my frame rate at 60?
First site that I saw with solutions:
Why is screen tearing happening? tl;dr - your GPU is under heavy load.
that can’t be true, especially in Overwatch with low/medium settings with a RX 590 4gb and a I7 processor.
Meh, I’ve decided shortly after posting this It’s time to get a new monitor. I’m probably completely unaware how bad 60hz really is in 2019 until I get a upgrade and experience 120/140hz for myself.
Cap in-game at 59. Tbh though it sounds like a monitor issue.
Capping frames limits yes BUT doesnt sync with monitor so if using a nv card try turning on adaptive vsync in nvidia settings.
Download DDU run it… select the option to boot into safe mode after uninstalling drivers and reinstall with only physX and driver nothing else.
yeah it probably is I’ve had this monitor for 5+ years, it’s done me good but It’s about time I get a upgrade really.
Best way to get rid of screen tearing: buy a higher refresh rate monitor(if your GPU can handle it.) I use an Acer XFA240 144hz monitor. Night and day difference. The frames are going so fast you wont see the tearing. I cant even go back to 60hz now. Also: vsync = input lag
Read my edit …try that too
That’s precisely how it works. Tearing will happen if you don’t use any form of sync, be that vsync, freesync, gsync, enhanced sync, fast sync, etc.
There’s no way around. A common solution you hear parroted a lot is that one should push FPS higher than the refresh rate. That is a myth. Higher FPS is a palliative, tear will be less visible, but it’s not a fix.
No, it is not. That list is very misguiding.
You can use Rivatuner Statistics Server to fix the screen tearing.
This FPS limiter has a feature called scanline sync.
With scanline sync you can lock the tearline in you screen where
you can’t see it anymore.
Sorry for my bad english, but i hope i could help 
Download:
h ttps://www.guru3d.com/files-details/rtss-rivatuner-statistics-server-download.html
Tutorial:
h ttps://forums.guru3d.com/threads/requesting-scanline-sync-tutorial.423722/#post-5602543
I run overwatch with no framelimitation and that fixed tearing for me (60hz display 200-250 fps)
Turn off vsync and turn of the 60 fps cap.
Alternatively if you have a nvidia card go into control panel and turn adaptive vsync on (vsync option off in game)
That is very interesting.
Yes, it might be your monitor. I was using an old monitor and the thing kept going out on me randomly. I switched the old monitor with a newer monitor from a second pc and the problem went away.
If your GPU can maintain more than 60 FPS…
Set the in-game framerate to custom with a limit of 300.
Then go into your Nvidia control panel, program settings, Overwatch and enable fast sync under the v-sync options.
Make sure in-game v-sync is set to off, and triple buffering also off.
Of course you get screen tearing, capping the FPS at 60 won’t sync the frames, it just makes your PC generate 60 frames only.
You either don’t cap your framerate or cap at a higher framerate: I use 75 FPS with vsync off and there’s no tearing but anything from 55-74 WILL cause tearing and visible stutters.
I’m no expert but if there’s some kind of software sync it has to generate input lag as well doesn’t it?
Your misunderstanding is due to not understanding how monitors work. A 60hz monitor does not simply display an image, then wait 16ms, then display another one. The image is actually being scanned out to your display over the course of that 16ms.
Enabling vsync is a way of saying “I dont want you to display this image until the previous one has been completely scanned out.” This means you’re forced to wait up to 16ms until the display is ready for a new frame, and then you give it one.
Simply capping your framerate to your monitor’s refresh rate doesn’t do this at all. It provides the new frame to the monitor literally the moment it’s available. If the monitor has only scanned out half of the previous image… well too bad. The bottom of your screen is now the new image (and thus, you have tearing).
Vsync comes at a terrible price which is due to that synchronization, it effectively “queues” frames. If you cap your framerate while vsync is enabled, you’ll get the minimal amount of latency because the worst case is you’ll wait no more than 16ms. However if you dont cap your framerate while vsync is enabled, your computer can generate frames faster than your monitor can display it. The operating system will usually prevent any more than 3 frames to be rendered and displayed before it blocks the application from doing so any further. This is why vsync is awful for input latency. What you see on screen could literally be something you rendered 48+ milliseconds ago.
There are ways to mitigate this and have a bit of a middle grounds – for example I believe nvidia has an option called ‘fast sync’, which is probably your best bet.
Alternatively you can actually render significantly higher than your framerate. You’ll get more tears on the screen, but they will be less noticeable (because there will be less of a difference frame to frame). For anyone who dislikes tearing, this is probably not a good option unless you can really crank up the frames (i.e. 200+). Even then you’ll still likely notice it.
that’s exactly what vsync is supposed to do, what is there to be confused about??
Click the tutorial link in my post, stay on page 1 and scroll down to the last post this guys explained how the latency is working.