Elden Ring Gets Free AMD FSR 3 Frame Generation Mod

wccftech.com:

It's been a year and a half since PureDark released his Elden Ring NVIDIA DLSS 3 Frame Generation mod. The paid mod allowed GeForce RTX 40 Series owners a significant performance boost in the notoriously badly optimized game developed by FromSoftware.

However, everyone else without an RTX 40 Series GPU has been out of luck so far. That changes with the recently released free AMD FSR Frame Generation and Temporal Super Resolution (ERSS-FG) mod by Nexus Mods user huutaiii.

Related Story Leaked Mod Let’s You Enable AMD FSR 3 “Frame Generation” In Any FSR 2 Game, Supports Both AMD & NVIDIA GPUs

This mod supports AMD FSR 3 Super Resolution and Frame Generation, NVIDIA DLSS Super Resolution and DLAA, and even Intel XeSS. The modder shared a few caveats: this is mutually exclusive with their previous ERSS2 mod (which did not support Frame Generation); the Frame Generation feature is not compatible with ReShade; and, most importantly, you can't play online on official servers with this mod enabled.

Here's the recommended installation method for this Elden Ring AMD FSR 3 mod:

• Extract the attached file's content into the ELDEN RING\Game\ directory (including ERSS-FG.dll, dxgi.dll and the folder ERSS2; the file ERSSReShadeStub.addon can be removed).
• Disable Easy Anti-Cheat, either by putting cmd /c start eldenring.exe & rem %command% in launch options in Steam or by using some other tool.
• For Steam Deck (Linux) users: cmd=(%command%); cmd[-1]="eldenring.exe"; WINEDLLOVERRIDES="dinput8=n,b;dxgi=n,b" "${cmd[@]}"
• Set Resolution in the game's Graphics menu to .r target resolution (i.e. your monitor's resolution)
• Open the mod's configuration overlay with the Home key, set Frame Generation method to AMD FSR then restart, and set Super Sampling setting to the upscaling technology of your choice

There are several known issues with the current release of this Elden Ring AMD FSR 3 mod, though:

• Flickering global illumination, most visible in shaded areas
  Workarounds:
  • Restarting the