Screen tearing in steam client

[ZumZoom]

It's pretty bad when scrolling. Did this happen with a recent update for anyone? Or do I need to reinstall my gpu driver again?
https://www.vsynctester.com/ shows vsyncmark ~130, which is almost the same as firefox, but the latter works fine. I thought steam used Edge as the browser, or is it chromium? In both cases it's weird since those browsers have very good graphs on vsynctester.

[Lavie]

Hi!

In Steam setting under "Interface" their some options you can try.

[【๖ۣۜ.#נυѕтƒαмє™】]

Originally posted by NovigradNomad:

Screen tearing can indeed be frustrating. If you're experiencing screen tearing in the Steam client, here are a few steps you can try to address the issue:

1. **Update GPU Drivers**: Ensure that you have the latest graphics card drivers installed. Sometimes, outdated or corrupted drivers can cause screen tearing. Download and install the latest drivers from the manufacturer's website.

2. **V-Sync**: In the Steam client settings, you can try enabling V-Sync. This option helps prevent screen tearing by synchronizing your graphics card's frame rate with the refresh rate of your monitor.

3. **Disable Hardware Acceleration**: Some users have reported that disabling hardware acceleration in the Steam client can help reduce screen tearing. You can find this option in the Steam settings.

4. **Browser Rendering**: Steam's built-in web browser uses a version of Chromium. You might want to experiment with different browser rendering options (like hardware acceleration) to see if that improves the situation.

5. **Monitor Refresh Rate**: Ensure that your monitor's refresh rate is set correctly in both your display settings and your graphics card settings. Mismatched refresh rates can lead to screen tearing.

6. **Limit Frame Rate**: You could also try using a third-party application to limit the frame rate of the Steam client. This can help reduce screen tearing by preventing the frame rate from exceeding your monitor's refresh rate.

My man out here posting chat gpt answers on multiple threads.

[ZumZoom]

Thanks for the replies. Looks like it fixed itself after I disabled and then re-enabled hardware acceleration.

[Lavie]

[nightmarexfrx]

Originally posted by ZumZoom:

Thanks for the replies. Looks like it fixed itself after I disabled and then re-enabled hardware acceleration.

Can confirm. I had screen tearing in client after installing GeForce driver 545.92 (skipped 1 or 2 before that so problem could have been with previous drivers as well). I turned of GPU accellerating for "web views" prompting a restart; issue persisted; re-enabled prompting another client restart; issue resolved.

[The Foxiest]

Originally posted by ZumZoom:

Thanks for the replies. Looks like it fixed itself after I disabled and then re-enabled hardware acceleration.

Dude, thank you. Seriously.

I have been dealing with this for a while, unable to figure out why my PC has had screen tearing issues sometimes but not others. I never considered it was just the steam client itself (Some game have screen tearing for me as well).

Even though it doesn't really mean anything, I awarded your answer.

[ZumZoom]

Originally posted by The Foxiest:

Originally posted by ZumZoom:

Thanks for the replies. Looks like it fixed itself after I disabled and then re-enabled hardware acceleration.

Dude, thank you. Seriously.

I have been dealing with this for a while, unable to figure out why my PC has had screen tearing issues sometimes but not others. I never considered it was just the steam client itself (Some game have screen tearing for me as well).

Even though it doesn't really mean anything, I awarded your answer.

Glad it helped you. Thanks for the points!

[Blue]

turning on and off hardware acceleration didn't help me for some reason </3

[Alice Liddell]

Originally posted by V4ULT_HUNT3R:

turning on and off hardware acceleration didn't help me for some reason </3

How about turning on HAGS and leaving it on? (The one in Windows not Steam Client).

Works on Win10 not sure why Win11 has it off by default now (Perhaps because Win11 is a buggy mess).

The issue reminds me of the same issue when they were testing out a feature on Win10 for use on Win11 which was called, Memory Integrity.