Vsync because it syncs your GPU to your refresh rate.

like everything in PC it will depend on the game you are trying to play.....something like fallout 4 needs to be capped at 60 frames regardless of monitor unless you do mods to the game.....

sort of

vsync only output complete frames to the display

gpu draws frames and stores them in the frame output buffers, which sends them to the display

with all forms of gsync off, as soon as a frame is complete its sent to the display, even mid frame sends, causing tear lines

vsync will complete sending the latest completed frame, at the start of new refresh it will send the next/latest completed frame

can cause some delays

ex. vsync off
dra -> send -> w -> repeat

vsync on
draw -> wait -> send -> repeat

gsync/freesync, will lower the displays refresh rate, forcing refresh at each new frame
only really useful for when fps is lower than the displays max refresh

There is no "real answer". It depends on what you're doing and what you want to prioritize.

Vsync synchronizes the vertical scan-out from your GPU to your display at the same fixed refresh rate of the display. It does this by using a buffer (or multiple-stages of buffer) so that the GPU will finish rendering a full frame and store it in the output buffer. It will then start to work on the next frame; if it is able to complete the next full frame before the scan-out to the display occurs the buffer is updated with that newer frame, otherwise the scan-out will scan the existing buffered frame out to the display.

This buffering of the output is why Vsync adds additional latency because you are essentially getting at least 1 frame "old" image data always. This also is why Vsync will suffer from what is perceived as stutter. Because what image is in the output buffer can vary and may not be the "next" frame sequentially that the GPU has completed rendering. When the GPU is able to complete more than 1 frame before the refresh rate scans out the buffer there will be a perceived "jump" or "hitch" in the framerate.

Vsync OFF with a frame rate cap will still not prevent screen tearing because the frame rate can still be lower than the refresh rate which will still result in two different partial frames being scanned out to the display and thus will have a tear line. But if your GPU for whatever game you are playing is always above your display's refresh rate, then setting a frame rate cap will give you a similar result to using Vsync but without the added input latency from buffering the output. You will still get more noticeable stutter/hitching with this however because your GPU is going to output whatever the most recent full frame is when you have a frame rate cap enabled. So you will not be getting "evenly paced frames".

Gsync/VRR "fixes" those limitations by reversing what is "syncing"; e.g. it will variably refresh the display as soon as the GPU is ready to output a new frame.

https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/

Blurbuster's Gsync 101 guide explains how each of these display settings works and what the tradeoffs are for them.

Turn off adaptive frame rate and try to balance constant frame rate and refresh rate manually before resorting to that crutch.

Sync often makes things worse. Quite often painful input lag can be dealt with by just shutting off all sync and post processing. Even if there's a bit of tearing, that's a small price compared to it being unplayable.

引用自 PopinFRESH：

There is no "real answer". It depends on what you're doing and what you want to prioritize.

Vsync synchronizes the vertical scan-out from your GPU to your display at the same fixed refresh rate of the display. It does this by using a buffer (or multiple-stages of buffer) so that the GPU will finish rendering a full frame and store it in the output buffer. It will then start to work on the next frame; if it is able to complete the next full frame before the scan-out to the display occurs the buffer is updated with that newer frame, otherwise the scan-out will scan the existing buffered frame out to the display.

This buffering of the output is why Vsync adds additional latency because you are essentially getting at least 1 frame "old" image data always. This also is why Vsync will suffer from what is perceived as stutter. Because what image is in the output buffer can vary and may not be the "next" frame sequentially that the GPU has completed rendering. When the GPU is able to complete more than 1 frame before the refresh rate scans out the buffer there will be a perceived "jump" or "hitch" in the framerate.

Vsync OFF with a frame rate cap will still not prevent screen tearing because the frame rate can still be lower than the refresh rate which will still result in two different partial frames being scanned out to the display and thus will have a tear line. But if your GPU for whatever game you are playing is always above your display's refresh rate, then setting a frame rate cap will give you a similar result to using Vsync but without the added input latency from buffering the output. You will still get more noticeable stutter/hitching with this however because your GPU is going to output whatever the most recent full frame is when you have a frame rate cap enabled. So you will not be getting "evenly paced frames".

Gsync/VRR "fixes" those limitations by reversing what is "syncing"; e.g. it will variably refresh the display as soon as the GPU is ready to output a new frame.

https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/

Blurbuster's Gsync 101 guide explains how each of these display settings works and what the tradeoffs are for them.

Thanks. I have a freesync monitor. so is it ok to disable vsync and limit fps to 176 fps? Do I have the best feel when playing or would everything be smoother if I played it better with Vsync? I have a 180 Hz monitor. Unfortunately there is a problem with the rx 9070 cards that Vsync does not work when freesync is activated, I am forced to limit the fps. ingame Vsync doesn't work because of this bug. Only vsync works in the driver but unfortunately this causes problems with the adrenaline vsync in some games, I'm forced to limit the fps.

引用自 Cheetah：

引用自 PopinFRESH：

There is no "real answer". It depends on what you're doing and what you want to prioritize.

Vsync synchronizes the vertical scan-out from your GPU to your display at the same fixed refresh rate of the display. It does this by using a buffer (or multiple-stages of buffer) so that the GPU will finish rendering a full frame and store it in the output buffer. It will then start to work on the next frame; if it is able to complete the next full frame before the scan-out to the display occurs the buffer is updated with that newer frame, otherwise the scan-out will scan the existing buffered frame out to the display.

This buffering of the output is why Vsync adds additional latency because you are essentially getting at least 1 frame "old" image data always. This also is why Vsync will suffer from what is perceived as stutter. Because what image is in the output buffer can vary and may not be the "next" frame sequentially that the GPU has completed rendering. When the GPU is able to complete more than 1 frame before the refresh rate scans out the buffer there will be a perceived "jump" or "hitch" in the framerate.

Vsync OFF with a frame rate cap will still not prevent screen tearing because the frame rate can still be lower than the refresh rate which will still result in two different partial frames being scanned out to the display and thus will have a tear line. But if your GPU for whatever game you are playing is always above your display's refresh rate, then setting a frame rate cap will give you a similar result to using Vsync but without the added input latency from buffering the output. You will still get more noticeable stutter/hitching with this however because your GPU is going to output whatever the most recent full frame is when you have a frame rate cap enabled. So you will not be getting "evenly paced frames".

Gsync/VRR "fixes" those limitations by reversing what is "syncing"; e.g. it will variably refresh the display as soon as the GPU is ready to output a new frame.

https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/

Blurbuster's Gsync 101 guide explains how each of these display settings works and what the tradeoffs are for them.

Thanks. I have a freesync monitor. so is it ok to disable vsync and limit fps to 176 fps? Do I have the best feel when playing or would everything be smoother if I played it better with Vsync? I have a 180 Hz monitor. Unfortunately there is a problem with the rx 9070 cards that Vsync does not work when freesync is activated, I am forced to limit the fps. ingame Vsync doesn't work because of this bug. Only vsync works in the driver but unfortunately this causes problems with the adrenaline vsync in some games, I'm forced to limit the fps.

That isn't a problem; that is by design. You are using either Freesync OR Vsync.

If you have an RX9070 and a freesync compatible display then I'd suggest for most things you use Freesync and similar to the Gsync guide set a frame rate cap to 2fps lower than your display's max refresh rate. In reality Freesync is not the exact same as Gsync and has a different behavior than Gsync when your frame rate exceeds the refresh rate.

With Gsync when your frame rate is higher than your refresh rate the Gsync system will engage a "Gsync Ceiling" by essentially dynamically turning on Vsync and buffering the output when frame rate exceeds the ceiling. This results in undesired input latency at random whenever the FPS goes above your max refresh rate. This is why they set an FPS cap to 2fps lower than your max refresh rate.

On Freesync it doesn't have the same behavior but when your frame rate exceeds the refresh rate when using Freesync you will start seeing multiple tear lines; also undesirable. So different reasons but if you turn on Freesync and then enable a frame rate cap to 2fps lower than your max refresh rate you'll end up with essentially the most consistent frame rate & frame pacing.

引用自 PopinFRESH：

引用自 Cheetah：

Thanks. I have a freesync monitor. so is it ok to disable vsync and limit fps to 176 fps? Do I have the best feel when playing or would everything be smoother if I played it better with Vsync? I have a 180 Hz monitor. Unfortunately there is a problem with the rx 9070 cards that Vsync does not work when freesync is activated, I am forced to limit the fps. ingame Vsync doesn't work because of this bug. Only vsync works in the driver but unfortunately this causes problems with the adrenaline vsync in some games, I'm forced to limit the fps.

That isn't a problem; that is by design. You are using either Freesync OR Vsync.

If you have an RX9070 and a freesync compatible display then I'd suggest for most things you use Freesync and similar to the Gsync guide set a frame rate cap to 2fps lower than your display's max refresh rate. In reality Freesync is not the exact same as Gsync and has a different behavior than Gsync when your frame rate exceeds the refresh rate.

With Gsync when your frame rate is higher than your refresh rate the Gsync system will engage a "Gsync Ceiling" by essentially dynamically turning on Vsync and buffering the output when frame rate exceeds the ceiling. This results in undesired input latency at random whenever the FPS goes above your max refresh rate. This is why they set an FPS cap to 2fps lower than your max refresh rate.

On Freesync it doesn't have the same behavior but when your frame rate exceeds the refresh rate when using Freesync you will start seeing multiple tear lines; also undesirable. So different reasons but if you turn on Freesync and then enable a frame rate cap to 2fps lower than your max refresh rate you'll end up with essentially the most consistent frame rate & frame pacing.

I can't explain it better, thank you very much. So then it's not a bug that ingame vsync doesn't work, it's intentional because the two don't get along properly? I come from an Nvidia and Vsync ingame with gsync worked without any problems. So if I understood you correctly it's perfect freesync and limited to 178 fps right?

引用自 Cheetah：

引用自 PopinFRESH：

That isn't a problem; that is by design. You are using either Freesync OR Vsync.

If you have an RX9070 and a freesync compatible display then I'd suggest for most things you use Freesync and similar to the Gsync guide set a frame rate cap to 2fps lower than your display's max refresh rate. In reality Freesync is not the exact same as Gsync and has a different behavior than Gsync when your frame rate exceeds the refresh rate.

With Gsync when your frame rate is higher than your refresh rate the Gsync system will engage a "Gsync Ceiling" by essentially dynamically turning on Vsync and buffering the output when frame rate exceeds the ceiling. This results in undesired input latency at random whenever the FPS goes above your max refresh rate. This is why they set an FPS cap to 2fps lower than your max refresh rate.

On Freesync it doesn't have the same behavior but when your frame rate exceeds the refresh rate when using Freesync you will start seeing multiple tear lines; also undesirable. So different reasons but if you turn on Freesync and then enable a frame rate cap to 2fps lower than your max refresh rate you'll end up with essentially the most consistent frame rate & frame pacing.

I can't explain it better, thank you very much. So then it's not a bug that ingame vsync doesn't work, it's intentional because the two don't get along properly? I come from an Nvidia and Vsync ingame with gsync worked without any problems. So if I understood you correctly it's perfect freesync and limited to 178 fps right?

Correct, on Nvidia's side they handle the "above max refresh rate" differently and the driver essentially will just ignore the in-game vsync setting when you've enabled Gsync and "override" it with whatever the setting is configured as in the NVAPP / NVCP.

On AMD's side just enable Freesync and in Catalyst Control Center set a global frame rate cap by enabling "Frame Rate Target Control" and then in advanced set the target cap to 2fps lower than your max refresh rate for your displays VRR range. So if your display's max VRR range is 180Hz then you'd set the target cap to 178fps like you're noting. If it's 144Hz you'd set it to 142fps, etc.

引用自 PopinFRESH：

引用自 Cheetah：

I can't explain it better, thank you very much. So then it's not a bug that ingame vsync doesn't work, it's intentional because the two don't get along properly? I come from an Nvidia and Vsync ingame with gsync worked without any problems. So if I understood you correctly it's perfect freesync and limited to 178 fps right?

Correct, on Nvidia's side they handle the "above max refresh rate" differently and the driver essentially will just ignore the in-game vsync setting when you've enabled Gsync and "override" it with whatever the setting is configured as in the NVAPP / NVCP.

On AMD's side just enable Freesync and in Catalyst Control Center set a global frame rate cap by enabling "Frame Rate Target Control" and then in advanced set the target cap to 2fps lower than your max refresh rate for your displays VRR range. So if your display's max VRR range is 180Hz then you'd set the target cap to 178fps like you're noting. If it's 144Hz you'd set it to 142fps, etc.

Thank you so much. Now I understand it how Gsync and Freesync works :)

引用自 smokerob79：

like everything in PC it will depend on the game you are trying to play.....something like fallout 4 needs to be capped at 60 frames regardless of monitor unless you do mods to the game.....

what ? not true

i use gsync a nd vsync together at all times rarely ever have to change it.and every now and then i will use ELMB like in farcry 4 its the only thing ive found that will get rid of the stutter in that game

引用自 Guydodge：

引用自 smokerob79：

like everything in PC it will depend on the game you are trying to play.....something like fallout 4 needs to be capped at 60 frames regardless of monitor unless you do mods to the game.....

what ? not true

i use gsync a nd vsync together at all times rarely ever have to change it.and every now and then i will use ELMB like in farcry 4 its the only thing ive found that will get rid of the stutter in that game

Given the title mentioned I think he is intending to point to a limitation with the game engine; not so much with the display. The version of Creation Engine that Fallout 4 uses (and older versions) have limitations for cutscenes that can cause issues with the cutscenes at higher frame rates. E.g. animations being broken and/or out of sync, audio and animation being out of sync, etc. But I'm pretty sure it's been patched since launch to where it will cap frame rate during cutscenes regardless of your settings.

I'll copy and paste from something I read a bit back.

"Recommended configuration

NVIDIA Control Panel:
Turn VSync ON.
Set the G-Sync mode to "Enable G-Sync" for full-screen or windowed mode.
Consider setting Low Latency Mode to "Ultra" to further reduce input lag and frame rate cap
your performance just below your monitor's refresh rate.
In-game settings:
Turn VSync OFF.
It is generally best to disable the in-game frame rate limiter, as the NVIDIA Control Panel will
now handle the frame rate cap.

Why this works

Prevents screen tearing: V-Sync ensures the GPU waits for the monitor to finish its current
frame before displaying the next one.

Avoids input lag: When your frame rate is within the G-Sync range, V-Sync in the Control
Panel does not add extra input lag.

Eliminates stutter: V-Sync in the Control Panel prevents your frame rate from dropping
below the G-Sync range, which eliminates stuttering and tearing when your frame rate
exceeds the monitor's refresh rate."

Personally I don't use G-Sync or Vsync but rather balance my frame times somewhere between the P1 and P5 values and you don't need either of them, for this though ideally you need a top tier CPU and GPU so the average FPS is still decent when between P1 and P5, or at least if you want to play on max settings.

Some in game Vsync is terrible also and it's not always implemented equal in all games.