I shall test this morning for you and report back.
Call of duty Black ops 6
- Thread starter sgoaty
- Start date
Do you have Vsync enabled or disabled? If you have it disabled you will still get screen tearing in some games because frame rate limiters aren't perfect. Vsync doesn't add any latency when used in combination with freesync/g-sync.
Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,604
- Location
- Cornwall
Disabled.
It's not so much the latency is how your teammates dropped in steps rather than smoothly when vsync is enabled. Although I'm not sure if that still applies if freesync is being used. Not sure why it wouldn't though if vsync is done in game and freesync is done in drivers.
When Vsync is used with Freesync, all it does is prevent screen tearing by holding the frame until your display is ready when the frametime variance goes outside the Freesync range.
G-SYNC 101 - Blur Busters - Page 15
G-SYNC Module The G-SYNC module is a small chip that replaces the display's standard internal scaler, and contains enough onboard memory to hold and process a single frame at a time. The module exploits the vertical blanking interval (the span between the previous and next frame scan) to...
blurbusters.com
Last edited:
I switched to an AMD GPU (9070 XT) and found the same problem with the FPS cap which worked perfect on Nvidia. When I set it above 125fps it will jump up to 143fps which is too high for Freesync to work, and when I tried setting it to 120fps it jumped up to 125fps. Radeon chill limits it correctly if you set it from the game (not global), I'm not sure if it adds any input lag compared to the in-game limiter though. Do either of you know if it's a recent bug or has it always been broken with AMD GPUs?
I don't suppose your GPU temp works? My 9070XT just shows 0deg in the in-game indicator.
Mine also shows 0. Unfortunately capping the frame rate with Radeon chill does add a small amount of extra latency. A quick Google search suggests that the in-game frame cap has been an issue since MW3 for AMD GPUs. It occurred to me that I had an issue with screen tearing on MW3 when setting the frame cap above 120fps, which was odd because I never noticed screen tearing on MW2 at 140fps. I wonder if the in-game fps limiter might have also been broken on Nvidia cards but there was an additional bug that reported the fps incorrectly. The solution on Nvidia was to set V-Sync on and low latency mode to ultra in the control panel, which automatically capped the fps slightly below the refresh rate and didn't add any extra latency.
I had the same issue when I previously tried an AMD GPU (6900xt) in the original WZ ~2021, and the problem still seems to be present today. There are clearly some set numbers that work, 200fps and 250fps do, but anything in between it just skips to the next highest working fps limit. It's very strange.
Last edited:
I found that if you can get the in-game fps limiter at least 1 frame below your refresh rate on a freesync monitor then turning on v-sync doesn't add any input lag, which is lucky for me on a 144Hz screen because I can get the in-game limiter at 143fps.
Been that way for some time, it's why us Gsync users do it around 3 fps below max HZ.. So on mine it's 162 out of 165hz
Although I do it in Nvidia control panel
Last edited:
Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,604
- Location
- Cornwall
So, seems like an insanely big patch. Hope it's worth it, although annoyingly they seemed to improve the new sniper just after I got the Dark Matter skin on it.
Anyone else on an AMD card find the game crashes a lot or is it just MY AMD card?
Anyone else on an AMD card find the game crashes a lot or is it just MY AMD card?
Quite possible something else in the system also?
I've not had any crashes at all in Warzone on either Nvidia or AMD.
Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,604
- Location
- Cornwall
Hard to pinpoint is the issue, which is why I was asking in case it was a common thing.
When I start a game the AMD drivers crash and then the game crashes. Sometimes get a blue screen too. It's fine in the menu and stuff but as soon as the game is about to start it happens.
Yeah that's a strange one. I've not heard of any friends on either brands having any issues either. Certainly an instability somewhere. Have you tried RAM with EXPO/DOCP/XMP off and tried again?
Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,604
- Location
- Cornwall
I didn't seem to get it with my old card (I RMA'd it because one of the HDMI ports wasn't working and was sent a B-Grade card as a replacement).
I did initially get some issues (with my original card in this build) but I think I managed to clear most of them up by moving around the power cables on my PSU. It's a semi-new build, re-used GPU, CPU, RAM, PSU, cooler, case and some storage. New motherboard and some new storage. And then the replacement GPU.
Is it only this game it does it on or are there others? I've read that many folk had issues and had to clear game cache (unsure how).
Maybe time for some stability testing
Last edited:
Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,604
- Location
- Cornwall
I've not really tried other games, not sure what to try. I've run the Adrenaline stability test, OCCT, Heaven and done the GPU render in Cinebench 2024 and didn't seem to get it during them.
But anyway, didn't mean to turn this into a tech support thread for my GPU issue (discussing it in the AMD driver thread), just wondered if it might be somewhat common or known about on AMD cards.
