What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
AMD released updated Unreal Engine plugins for FidelityFX Super Resolution 3.1.3 and Radeon Anti-Lag 2.0.2 on February 3, 2025. Both updates add support for Unreal Engine 5.5, while the FSR plugin also introduces a new control for distortion effects during frame interpolation.
This is primarily an integration and compatibility release for developers—not a consumer driver update or a new generation of FSR.
As an Amazon Associate I earn from qualifying purchases.
What AMD released
| Plugin | Version | Main changes |
|---|---|---|
| AMD FidelityFX Super Resolution | FSR 3.1.3 | Updated FSR code, Unreal Engine 5.5 support, and a distortion-texture console variable |
| Radeon Anti-Lag 2 | 2.0.2 | Unreal Engine 5.5 support |
AMD’s FSR Unreal Engine guide and Anti-Lag 2 documentation provide the integration details. Contemporary release coverage from VideoCardz identified February 3, 2025, as the release date.
Why UE 5.5 support mattered
Unreal Engine 5.5 launched in November 2024, so developers moving projects to the newer engine needed plugin builds compatible with its APIs, modules, and rendering changes. The February update gave UE 5.5 projects an AMD-supported integration instead of requiring teams to keep older plugins or make their own source adjustments.
#1 Best Overall
- Axial-tech fans now feature a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- 2.5-slot design allows for greater build compatibility while maintaining cooling performance
- 0dB technology lets you enjoy light gaming in relative silence
- Dual BIOS switch lets you toggle between Quiet and Performance BIOS profiles
- Dual ball fan bearings last up to twice as long as sleeve bearing designs
Compatibility support does not add these technologies to existing games automatically. Developers must install the plugins, configure them, test the project, package the required files, and ship an update before players can benefit.
What changed in the FSR 3.1.3 plugin
FSR 3 combines temporal upscaling with optional frame generation. It reconstructs frames using information such as the rendered image, depth, and motion vectors, then interpolates additional frames between traditionally rendered frames. FSR 3.1 also separated frame generation from upscaling, allowing developers in principle to pair FSR frame generation with another upscaler when the game’s rendering pipeline supports that arrangement. See AMD’s FSR 3.1 announcement for the architectural context.
FSR 3.1.3 remains an incremental revision within the FSR 3.1 family. It should not be presented as FSR 4 or as a completely new reconstruction method. Its concrete Unreal-focused changes were the FSR code update, UE 5.5 compatibility, and a new console variable:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallr.FidelityFX.FI.UseDistortionTextureDistortion-texture control
This setting determines whether frame interpolation uses Unreal Engine’s distortion texture. That can matter in scenes with heat haze, refraction, water, glass, or other material and screen-space distortion effects.
It is a targeted integration control, not a universal image-quality switch. Whether it helps depends on the project’s distortion effects, whether the texture is generated correctly, and which artifacts appear in the game. Developers should compare the setting in representative scenes rather than assume that enabling it always improves frame generation.
Rank #2
- Axial-tech fans now feature a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- Phase-change GPU thermal pad helps ensure optimal heat transfer, lowering GPU temperatures for enhanced performance and reliability
- 2.5-slot design allows for greater build compatibility while maintaining cooling performance
- Dual-ball fan bearings last up to twice as long as standard conventional sleeve bearings designs
- 0dB technology lets you enjoy light gaming in relative silence
What changed in Anti-Lag 2.0.2
Anti-Lag 2 is designed by AMD to reduce end-to-end system latency in GPU-bound scenarios by coordinating CPU and GPU work inside the game. The 2.0.2 Unreal plugin’s principal published change was UE 5.5 support; the available changelog did not identify a major new latency feature.
Anti-Lag 2 is intended to integrate with AMD’s FSR plugin when frame generation is enabled through the native Direct3D 12 path. That integration is important because frame generation adds another stage to the rendering pipeline. However, Anti-Lag 2 is not a substitute for a healthy base frame rate, and it cannot remove latency from the display, input devices, rendering pipeline, or generated-frame process.
AMD’s documentation also records an important limitation: the documented FSR frame-generation integration uses the native Direct3D 12 backend, and the Anti-Lag 2 plugin is not compatible with the RHI backend in the FSR 3.1.1 Unreal plugin. Developers should verify the exact compatibility notes for the plugin package they are using.
Requirements developers need to separate
There are four different compatibility questions:
- Engine compatibility: Does the plugin build support the project’s Unreal Engine version?
- Runtime hardware: Is the GPU architecture supported?
- Driver and API support: Is the required AMD Software and graphics API path available?
- Rendering integration: Does the game provide reliable motion vectors, depth, camera data, UI handling, and frame pacing?
AMD’s current Anti-Lag 2 documentation lists support for AMD RDNA 1-based products and newer, including Radeon RX 5000-series and later, on Windows 10 or Windows 11. It lists AMD Software: Adrenalin Edition 24.6.1 or newer for DirectX 11, 24.7.1 or newer for DirectX 12, and 24.9.1 or newer for Vulkan. These are current documentation requirements and should not automatically be treated as the exact requirements of the February 2025 plugin.
FSR’s broad vendor compatibility does not mean that every GPU, API, or game configuration behaves identically. Developers should test across GPU vendors and relevant graphics APIs, with and without frame generation.
Rank #3
- System Compatibility Note: 2.5‑slot card measuring 303 mm (L) x 131 mm (W) x 45 mm (H); requires a single 8‑pin power connector and a recommended 550W power supply. Please verify chassis clearance and power supply capacity before purchase.
- Dedicated Support: Please contact us directly through Amazon for any product questions or assistance you may require.
- AMD RDNA 3 Architecture with AI & Ray Tracing Acceleration: Powered by 32 RDNA 3 Compute Units featuring 3rd Gen Ray Tracing Accelerators and 2nd Gen AI Accelerators, delivering lifelike lighting, shadows, and superior machine learning performance for enhanced gaming and content creation.
- Powerful 1080p & 1440p Gaming Engine: Features a max boost clock of up to 2695 MHz, a game clock of 2280 MHz, and 2048 stream processors, ensuring outstanding frame rates in the latest titles.
- 8GB High‑Speed GDDR6 Memory: Equipped with 8GB of GDDR6 memory on a 128‑bit interface running at 18 Gbps, delivering up to 288 GB/s bandwidth for high‑resolution textures and demanding game workloads.
Installation outline
AMD’s current Anti-Lag 2 workflow is broadly:
- Download the plugin archive and extract it.
- Place the
AntiLag2folder inEngine/Plugins/Marketplace, unless the package readme specifies a project-local or source-tree installation. - Open Unreal Editor and go to Plugins.
- Enable AntiLag2 and restart the editor.
- Configure it under Project Settings > Anti-Lag 2, or use
r.AMD.AntiLag2.
Install the matching FSR plugin using the directory and setup instructions included with its archive. Folder placement can differ between an installed engine, a source-built engine, and a project’s local Plugins directory. Do not assume that copying a nested archive folder directly into the destination will produce the correct plugin structure.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhat developers should test
- Base rendered frame rate and frame-time consistency before enabling frame generation.
- Motion vectors for animated meshes, foliage, particles, and materials.
- Disocclusions, transparency, camera cuts, rapid exposure changes, and post-processing.
- HUD and other interface elements, which may need separate handling to avoid interpolation artifacts.
- Water, glass, heat haze, and other distortion effects with
r.FidelityFX.FI.UseDistortionTextureenabled and disabled. - Latency and pacing with and without Anti-Lag 2 and frame generation.
- Packaging, runtime files, anti-cheat interactions, and multiple GPU/API combinations.
A higher FPS counter alone is not enough. Developers should distinguish base FPS from generated display frames, measure frame-time consistency, and use a suitable latency tool such as AMD’s Frame Latency Meter where appropriate.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common problems
The plugin does not appear in Unreal Editor
Check the folder nesting, destination directory, engine-version match, and whether the editor was restarted. A plugin archive may contain an extra top-level folder that must be moved up one level.
The project fails to build or package
The plugin may target a different Unreal minor version, require source-tree access, contain incompatible precompiled binaries, or fail to resolve module dependencies. Disable the plugin, back up the project, remove its Binaries and Intermediate directories, regenerate project files, rebuild, and then re-enable the plugin. Follow the specific archive’s readme if it documents a different recovery path.
Frame generation shows artifacts
Investigate missing or incorrect motion vectors, transparency, particles, UI capture, camera cuts, exposure changes, and distortion-texture handling. The new distortion setting can address a particular input to interpolation, but it will not fix every artifact source.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #4
- Powered by Radeon RX 9070 XT
- WINDFORCE Cooling System
- Hawk Fan
- Server-grade Thermal Conductive Gel
- RGB Lighting
Anti-Lag 2 does not activate
Verify the project setting and r.AMD.AntiLag2, then check the GPU architecture, driver, graphics API, plugin pairing, and native Direct3D 12 requirement for the documented FSR frame-generation path.
What this meant for players
The release mattered indirectly. It made it easier for developers with UE 5.5 projects to integrate newer AMD technologies, but it did not update shipped games or guarantee that every Unreal Engine 5.5 title would support FSR 3.1.3 or Anti-Lag 2.
Players may see higher displayed frame rates when a game implements frame generation, but that does not guarantee lower input latency or better image quality. Results depend on the base frame rate, the game’s motion data, UI treatment, frame pacing, hardware, driver, and graphics settings. Anti-Lag 2 is most relevant when the game is GPU-bound; it does not turn a CPU-limited game into a GPU-limited one.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
