Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/69447db3-806c-8006-b23b-7b480ecc717e
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== 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 🔧
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)