Blur Busters Forums

Chief Blur Buster wrote:Hello and welcome to Blur Busters forums!

(BTW, I fixed your YouTube Markdown code into UBB code ([/video] format tags) to make your videos show up as embedded)

Unfortunately, it's normal during "camera spinning" situations where camera orbits an object. This forces rapid panning of background, which amplifies tearing visibility. I have analyzed your video, frame by frame, and tearing is extremely visible at 60Hz during spinning situations. This is actually normal tearing for 60Hz. What is happening is that you're doing a spinning angle in third-person view, and this is well-known to me as a method of amplifying visibility of tearing -- it's the type of motion you are doing.

To reduce visibility of tearing, you'll want to consider:

1. Try getting a higher refresh rate monitor, like one from Official List of Best Gaming Monitors.
The higher the refresh rate, the less visible tearing is because the tearline is only visible for (1/Hz)th of a second. At 240Hz, a tearline is visible for only one-quarter the time period as at 60Hz. At 120Hz, a tearline is visible for only one-half the time period as at 120Hz. The tearing visibility in your video is normal; I've seen it before for ~100-150fps at 60Hz during "camera spinning" situations.

2. Alternatively, try a Low-Lag VSYNC ON trick. It might be low lag enough for you.

3. Alternatively, try 240Hz GSYNC. You get stutterfree, tearingfree, and lag nearly matching VSYNC OFF! (unlike 60Hz GSYNC) Finally low enough for eSports. There's almost no lag difference between GSYNC and VSYNC OFF when the refresh rate is set to 240Hz, observe the 1000fps VSYNC OFF result (in both) compared to frame-capped GSYNC.



(From GSYNC 101: Input Lag Tests of 240Hz which also tested VSYNC OFF input lag too at 60Hz versus 240Hz).

Also, remember that our tests have been showing same framerate at higher Hz has less lag. Which means 100fps@240Hz has less input lag than 100fps@144Hz, so the use of 240Hz has competitive benefits even if you can't do full 240fps.
-- Higher fps at same Hz is lower lag
-- Higher Hz at same fps is lower lag
-- Doing both is best (higher fps and higher Hz) but doing just one or the other still lowers input lag.

So i did this for testing purposes and i noticed that the tear appears to be shifting up and down lighting fast.

Sparky wrote:

So i did this for testing purposes and i noticed that the tear appears to be shifting up and down lighting fast.

The shifting up and down is caused by small variances in frame render time after the framerate cap.

Anyway, it looks like normal tearing. You can verify that by checking that the tearing shows up on your monitor, but not in screen capture like OBS. Higher framerates mean there are more tears per second, but each tear has a smaller displacement across it. Higher refresh rates mean each tear stays on the monitor for less time.

Sparky wrote:

So i did this for testing purposes and i noticed that the tear appears to be shifting up and down lighting fast.

The shifting up and down is caused by small variances in frame render time after the framerate cap.

Anyway, it looks like normal tearing. You can verify that by checking that the tearing shows up on your monitor, but not in screen capture like OBS. Higher framerates mean there are more tears per second, but each tear has a smaller displacement across it. Higher refresh rates mean each tear stays on the monitor for less time.

Frs4ken wrote:What further confuses me is that there are people that say they never notice screen tearing (with vsync off ofcourse). I don't understand this because the screen tearing and stutter i'm having in the 75-90 FPS range on a 60Hz monitor makes games almost unplayable. The 2 videos that i uploaded are an example of this, i locked the fps to 83 on RTSS and filmed it on slow-mo with my camera.

Glide wrote:Most people that say this also neglect to mention that they are playing games in borderless windowed mode with V-Sync “disabled” in the game but forced by the desktop compositor.
I noticed a lot of people complaining about screen tearing with the Windows 10 Creators Update which allows certain whitelisted games to bypass the compositor in borderless mode.

RealNC wrote:If you want to get a similar behavior as borderless in W7/W8 or pre-update W10, then you need to play in fullscreen (if possible) and enable Fastsync (nvidia) or Enhanced Sync (AMD).

RealNC wrote:The REAL solution, however, is a gsync (nvidia) or freesync (AMD) monitor. This is the only way to eliminate tearing AND microstutter at the same time without adding input lag.

RealNC wrote:

Glide wrote:Most people that say this also neglect to mention that they are playing games in borderless windowed mode with V-Sync “disabled” in the game but forced by the desktop compositor.
I noticed a lot of people complaining about screen tearing with the Windows 10 Creators Update which allows certain whitelisted games to bypass the compositor in borderless mode.

Yeah, +1 to that. Many people always play borderless, which in Windows 7 and 8 will never tear, regardless of the vsync setting. You get a bit of extra input lag, plus a bit of microstutter, in exchange for never tearing. But when they upgraded to W10 with latest updates, they were in for a surprise.

If you want to get a similar behavior as borderless in W7/W8 or pre-update W10, then you need to play in fullscreen (if possible) and enable Fastsync (nvidia) or Enhanced Sync (AMD). If you have a fast machine, the "low latency vsync" method (linked to by Chief above) will help.

The REAL solution, however, is a gsync (nvidia) or freesync (AMD) monitor. This is the only way to eliminate tearing AND microstutter at the same time without adding input lag.