Original Source: [FSR FG+ VSync/Freesync/프레임 제한 간단 테스트 해봄 - 라데온 마이너 갤러리](https://gall.dcinside.com/mgallery/board/view?id=radeon&no=15628&fcno=71223&fpno=71205)

The capture tool used for testing was **CapFrameX v1.8.1**.

The ability to view **DisplayTime** was initially introduced as a beta feature toward the end of last year and has since been officially released. To enable this metric, select **“Use ‘MsBetweenDisplayChanges’ metrics”** in the settings.

When analyzing the results, **DisplayTime is the most important metric to focus on**. It represents the actual frame intervals presented to the monitor and is therefore the most reliable indicator for identifying **frame pacing issues**. For proper analysis, DisplayTime should always be examined alongside **FrameTime**. If FrameTime remains stable while DisplayTime shows sudden spikes, this typically indicates a frame pacing problem.

The game used for testing was **Wuthering Waves**, chosen because it is one of the most accessible titles that supports **FSR Frame Generation**. Testing was conducted by moving back and forth in the **Jinju Fortress area**, the first major open field where players spend a significant amount of time.



1. **V-Sync + FreeSync enabled, no frame cap** This configuration showed the **most stable DisplayTime overall**.
2. **V-Sync only** Without FreeSync, DisplayTime spikes were observed whenever the frame rate dropped below the monitor’s refresh rate. In these situations, synchronization breaks, resulting in **visible screen tearing**. This behavior was also confirmed during testing, with tearing clearly noticeable in those sections.
3. **FreeSync enabled + frame rate capped at refresh rate −3 via RTSS** Noticeable DisplayTime instability was observed. Since Radeon GPUs do not support RTSS frame limiting with NVIDIA Reflex, frame rates must be capped using conventional methods, which often interferes with proper FreeSync behavior.
4. **FreeSync enabled + frame rate capped at refresh rate −3 via FRTC / driver-level limiter** With the frame rate capped using FRTC, DisplayTime became noticeably more stable, suggesting that **FreeSync was functioning as intended**.
5. **FreeSync enabled + frame rate capped at refresh rate −13 via FRTC / driver-level limiter** By applying a more aggressive cap below the refresh rate, DisplayTime became **even more stable**.
6. **FreeSync enabled + frame rate capped at refresh rate −13 via RTSS** Applying a larger frame rate cap through RTSS did not produce any noticeable improvement compared to previous results.
7. **V-Sync enabled + FreeSync enabled + frame rate capped at refresh rate −3 via FRTC / driver-level limiter** This setup combines both synchronization methods while applying a mild frame rate cap.



It’s worth noting that these tests were conducted **quickly and casually**, so the results should not be treated as definitive.

When limiting frame rates, the **in-game frame limiter should always be the first choice**, if available. If not, driver-level options such as **Radeon Chill or FRTC** can be considered.

However, **FRTC has several drawbacks**:

* It is a **global setting**
* It was originally designed for **older games**
* It can negatively affect baseline frame timing in some scenarios

Because of these limitations, it’s difficult to recommend FRTC as a default solution.

Results can also vary depending on whether **Anti-Lag 2** is enabled on a per-game basis. In some cases, using **both synchronization methods together with a small frame rate cap** may yield better results.

Ultimately, whether you rely on **CapFrameX data** or **personal perception**, the best approach is to find the settings that work best for you. There is **no single correct configuration**—if the image looks smooth and feels good on your screen, that’s the right setup to use.

Testing FSR FG with Vsync/Freesync/Frame limiter