Your Radeon RX 6000 desktop card can now use ML-based FSR Upscaling in supported games. Start by checking the driver and game integration, then compare image quality and frame delivery under consistent conditions. This guide explains the official route and the limits that matter before you change settings.
Does FSR 4.1 work on Radeon RX 6000?
Yes. FSR Upscaling 4.1 support for Radeon RX 6000 desktop graphics arrived with AMD Software: Adrenalin Edition 26.10.1 on 20 October 2026. The developer documentation now lists the upscaler as version 4.1.2. Check the driver package for your exact card before updating.
This is machine learning upscaling: it reconstructs a higher-resolution image from lower-resolution rendered frames. RX 6000 support uses an INT8 model. It does not unlock every feature under the FSR “Redstone” name: ML-based frame generation and the new Driver-Assisted Frame Pacing path still require RX 9000 hardware. Games can separately offer older analytical frame generation on RX 6000.
Check the game as well as the graphics card
A supported GPU and driver are only part of the requirement. The game must have a compatible integration. For the DirectX 12 driver upgrade route, FSR 3.1 or later integrations are eligible with Adrenalin 26.10.1 or later. Eligibility is not a promise that every game will upgrade: an application can pin an effect version and opt out of driver-provided versions.
| Game configuration | What to check |
|---|---|
| Native ML-based FSR Upscaling integration | Select it in the game; the menu may use the older FSR 4 name. |
| DirectX 12 with FSR 3.1 or later | Check support for the AMD Software upscaling upgrade. |
| Vulkan | Do not assume an older FSR integration qualifies. The documented automatic upgrade route requires FSR Upscaling 4.1.2 or later integrated into the game. |
| Only FSR 1, FSR 2 or an unsupported integration | The driver update alone does not establish eligibility for ML upscaling. |
Use the official supported-games information to check your title before troubleshooting settings. A game menu label alone does not establish which implementation is running.
AMD FSR Technologies and Supported Games
How to enable the official upscaling upgrade
- Install a compatible AMD driver for your exact desktop RX 6000 card. Version 26.10.1 introduced this support; read the release notes for the package you choose.
- Close the game. Open AMD Software: Adrenalin Edition, then Gaming, then Graphics.
- Enable AMD FSR Upscaling for the driver upgrade route.
- Launch a supported game and enable its FSR 3.1 or later upscaling option. If the game offers native ML-based FSR Upscaling, use that integration instead.
- Start with Quality mode as a comparison baseline. Keep frame generation off while assessing upscaling, and record the game build, driver, graphics API and output resolution.
These steps concern upscaling on RX 6000. Do not enable a separate ML frame-generation option expecting this card to gain RX 9000 feature support. You do not need to install the developer SDK to follow the player workflow.
Choose a mode for your output resolution
Quality is a useful starting point because it supplies more input pixels than Balanced or Performance. It is a testing recommendation, not a guarantee that it will look best or meet your frame-rate target. With dynamic resolution disabled and the standard scaling ratios, these are the approximate input resolutions:
| Mode | Standard scale per dimension | Input at 1920 × 1080 output | Input at 2560 × 1440 output |
|---|---|---|---|
| Native AA | 1.0× | 1920 × 1080 | 2560 × 1440 |
| Quality | 1.5× | 1280 × 720 | About 1707 × 960 |
| Balanced | 1.7× | About 1129 × 635 | About 1506 × 847 |
| Performance | 2.0× | 960 × 540 | 1280 × 720 |
Games may round dimensions or expose different options. Native AA uses the output resolution as its input, so it does not reduce the rendering resolution. More aggressive scaling reduces input detail, while reconstruction itself also takes GPU time. The useful result depends on the game, card, output resolution and mode.
Test motion and performance separately
Use this proposed comparison method to decide what works on your PC. It is not an HD OPTI benchmark result, and no FPS uplift is promised.
- Pick a repeatable save, built-in benchmark or short route. Keep weather, camera movement and graphics settings as consistent as the game allows.
- Fix the output resolution and disable dynamic resolution for the comparison. Keep frame generation off and use the same frame cap and synchronisation settings in each run.
- Compare native rendering with your usual anti-aliasing against FSR Quality. If the game offers a supported way to compare the older upscaler with the ML upgrade, keep the quality preset identical.
- Repeat each condition several times. Record average FPS and the frame-time trace with the same monitoring tool. If a cap holds both runs at the same FPS, record that limitation instead of claiming equal performance headroom.
- Inspect slow camera pans, fine fences, foliage, moving characters and particles. Compare normal play as well as still images. Write down any trails, unstable edges or lost detail.
- Try Balanced only after establishing the Quality baseline. Keep the mode whose image and frame delivery you prefer in the scenes you actually play.
A sharper still image and a smoother moving image are separate observations. Keep both in your notes. Likewise, an FPS counter is not a latency measurement, and adding frame generation later changes the comparison.
If hitching continues, compare the frame-time trace rather than treating a higher average FPS as proof that it is fixed.
High FPS but Game Still Stutters? How to Fix Frame Time Spikes
What to do when the option is missing or FPS barely changes
| Observation | Next check |
|---|---|
| AMD FSR Upscaling is missing | Confirm the exact GPU and installed driver package support the feature. |
| The game still lists FSR 3.1 | Recheck the supported integration and driver setting; an unchanged label alone does not prove failure or success. |
| A Vulkan game does not upgrade | Check the game’s integration version; older Vulkan FSR support is not enough to establish eligibility. |
| Quality and Performance give similar FPS | Check whether a frame cap is masking the difference before drawing conclusions about the upscaler. |
| One mode looks worse in motion | Return to the preferred mode and compare the same scene again before changing other settings. |
If a repeatable, uncapped comparison still shows little response to lower rendering resolution, investigate the wider performance limit before buying hardware. Treat that as a diagnostic lead, not proof of a CPU bottleneck.
How to Identify a CPU Bottleneck in Modern Gaming
FAQ
The official route uses a supported game integration and a compatible AMD driver. Adrenalin 26.10.1 introduced RX 6000 upscaling support. This guide does not require replacing game DLLs or installing the developer SDK.
RX 6000 gains ML-based upscaling. The current ML-based frame-generation feature and Driver-Assisted Frame Pacing require RX 9000 hardware. A game may offer separate analytical frame generation on older cards.
No. The documented DirectX 12 upgrade route covers eligible FSR 3.1 or later integrations with the required driver. Vulkan has a different integration requirement, and pinned effect versions can opt out of driver-provided upgrades. Check the individual game.
Start with Quality as a comparison baseline, then test Balanced or Performance if needed. Quality uses a standard 1.5× scale per dimension and Performance uses 2×, so Performance starts from fewer input pixels at the same output resolution. Compare motion and frame times on your own card before choosing.
