Openai/69447db3-806c-8006-b23b-7b480ecc717e

This conversation was exported from ChatGPT

gpt-5-2

User: Should we use Vsync on and limit fps slightly below refresh rate with freesync/vrr when using amd far frame generation?

Should we use Vsync on and limit fps slightly below refresh rate with freesync/vrr when using amd far frame generation?

Assistant: Short answer: yes — in most cases that’s the best setup, but with very specific settings when you use FreeSync/VRR + AM…

Short answer: yes — in most cases that’s the best setup, but with very specific settings when you use FreeSync/VRR + AMD FSR Frame Generation (AFMF / FSR 3 FG).

Here’s the clean, no-nonsense setup and why it works 👇

✅ Recommended setup (AMD GPU + FreeSync/VRR + Frame Generation)

1. Enable FreeSync / VRR

• In AMD Adrenalin → Display → FreeSync: ON
• In your monitor OSD → FreeSync / Adaptive Sync: ON

This is mandatory. Frame generation without VRR feels worse.

2. VSync: ON (but only at the driver level)

• AMD Adrenalin → Graphics → Wait for Vertical Refresh → ON
• In-game VSync → OFF

👉 This prevents tearing only when you exceed the VRR range, without adding constant input lag like traditional in-game VSync.

3. FPS limit slightly below refresh rate (VERY important)

Limit FPS to ~3–5 FPS below your monitor’s max refresh:

| Monitor | FPS cap | | ------- | ------- | | 144 Hz | 140–141 | | 165 Hz | 160–162 | | 240 Hz | 235–237 |

You can do this via:

• AMD Adrenalin → FRTC
• RTSS
• In-game limiter (if it’s stable)

⚠️ Do not rely on Frame Generation alone to cap FPS — it doesn’t behave like a real limiter.

🎮 Why this combo works best with Frame Generation

Without FPS cap:

• You hit refresh ceiling
• VSync engages hard
• Input latency spikes
• FG frames feel uneven

With FPS cap below refresh:

• VRR stays active 100% of the time
• No VSync “hard lock”
• FG frames stay smooth
• Lower perceived latency

This is especially important with AMD FG, because:

• It already adds some latency
• It’s more sensitive to VRR disengaging than NVIDIA Reflex + DLSS FG

❌ What NOT to do

• ❌ In-game VSync + Driver VSync → double latency
• ❌ No FPS cap → VRR breaks at ceiling
• ❌ VSync OFF everywhere → tearing with FG
• ❌ Chill instead of FPS cap → inconsistent pacing

🧠 Extra tips (worth doing)

• Enable Anti-Lag / Anti-Lag+ (unless the game explicitly warns against it)
• Avoid running above native refresh even if FG “can”
• If the game supports it: Use in-game limiter > RTSS > FRTC (in that order)

Bottom line

Best practice with AMD Frame Generation:

✔ FreeSync ON ✔ Driver VSync ON ✔ In-game VSync OFF ✔ FPS cap 3–5 below refresh

That gives you the smoothest frame pacing, lowest latency possible, and zero tearing with AMD FG.

If you want, tell me:

• your monitor refresh rate
• the game(s) you play
• whether you’re using AFMF or FSR 3 FG

I can give you exact per-game settings 🔧

User: Can you show me the AMD source?

Can you show me the AMD source?

Assistant: I couldn’t find an official AMD support page that explicitly says “enable V-Sync + VRR + frame cap when using Radeon fr…

I couldn’t find an official AMD support page that explicitly says “enable V-Sync + VRR + frame cap when using Radeon frame generation” (similar to how NVIDIA documents Reflex + DLSS 3), but there *are pieces of official AMD documentation and authoritative sources that support the logic behind that recommendation. Here’s what we do have from AMD plus corroborating technical guidance:

✅ 1. Official AMD on FSR / Frame Generation

• AMD’s FSR technologies page confirms that FSR Frame Generation is designed to generate intermediate frames as part of the presentation pipeline, and that it works in tandem with upscaling and latency-reduction technologies like Radeon Anti-Lag 2. It doesn’t give configuration advice, but it shows AMD’s intention for optimal use in games. GPUOpen

✅ 2. AMD FSR 3 Technical documentation

• The AMD FSR Frame Generation Swapchain manual notes how the VSync and variable refresh rate (VRR) interact with the frame generation swapchain — showing that the pacing logic takes both into account during presentation. GPUOpen This is important because it means the sync behavior isn’t ignored by the frame generation system.

🔎 3. AMD’s indirect recommendations / best-practice hints

While AMD hasn’t published a unified “gaming setup guide” yet like NVIDIA Reflex with DLSS, these technical and implementation docs make it clear:

• The pacing logic of FSR Frame Generation considers expected refresh rate targets. GPUOpen
• Frame generation presumes input framerates above a threshold (e.g., ~60 FPS) to avoid interpolation artifacts. GPUOpen
• AMD does not disclaim VRR or VSync usage; rather, pacing systems interact with them depending on modes. GPUOpen

🧠 Community + expert confirmation

Even though these are not official AMD marketing docs, they reflect what AMD engineers and experienced developers/testers have observed from AMD’s own technical releases:

• Enabling VSync with frame generation is widely suggested for correct pacing and to avoid tearing because VRR alone doesn’t cap above the refresh rate when FG drives effective outputs. Reddit
• Many guides recommend FPS limiting when using frame generation, since unbounded framerates can cause sync issues and tearing even with VRR. Medium
• Frame pacing issues with FG/VSync/VRR being misaligned have been reported when VSync is disabled. NeoGAF

📌 What’s missing from AMD docs but implied

AMD doesn’t yet publish one single authoritative “here’s how to configure GPU/driver/monitor for best experience with FSR Frame Generation + VRR” guidance like NVIDIA does with Reflex + DLSS.

However, the technical behavior of their frame pacing and swapchain code clearly relies on a stable presentation rhythm (which VRR + capped framerate + VSync provides). GPUOpen

🧩 Summary of the AMD-linked evidence

| Claim | Supported by AMD sources? | | --------------------------------------------- | ------------------------------------------------------ | | Frame Generation works with VRR | Implied by pacing docs, not explicitly a guide | | AMD FG benefits from syncing to refresh | Technical docs show pacing logic reacts to VSync/VRR | | Limits / caps help performance/tear avoidance | Recommended by reviewers, confirmed by pacing behavior | | AMD provides clear published settings guide | ❌ No official single page yet |

📌 If you want the actual AMD links to read yourself

Here are the authoritative docs I used above:

🔗 AMD FSR technologies overview — AMD official (FSR including Frame Generation) AMD FSR Technologies page (official) 🔗 AMD FSR Frame Generation manual / swapchain — AMD GPUOpen official docs AMD FSR Frame Generation Swapchain docs (official)

If you want, I can pull direct quotes or screenshots from the specific AMD technical documentation about frame pacing and how VSync/VRR interacts with the frame generation swap chain.