Check that FoveaXR works with your GPU and your game

FoveaXR needs a Direct3D 12 game on NVIDIA RTX 20, AMD RX 6000 or Intel Arc and newer, or a Direct3D 11 game on NVIDIA RTX 20 and newer.

By EncidXVII. Checked with FoveaXR 0.2.0. Updated .

FoveaXR 0.2.0 works in OpenXR and OpenVR (SteamVR) games that render with Direct3D 11 or 12. Direct3D 12 games work on NVIDIA RTX 20, AMD RX 6000 and Intel Arc cards and newer; Direct3D 11 games need an NVIDIA RTX 20 or newer. Games with anti-cheat and games that foveate themselves are left alone.

Your GPU and the game’s graphics API

Graphics API NVIDIA (Turing, RTX 20 and newer) AMD (RDNA 2, RX 6000 and newer) Intel Arc
Direct3D 11 Yes No No
Direct3D 12 Yes Yes Yes
Vulkan, OpenGL No No No
Linux, Direct3D 12 Experimental, with a driver that has fragment shading rate Experimental Experimental
Linux, Direct3D 11 No No No

On Linux, Direct3D 12 games are experimental and require more testing.

Why Direct3D 11 is NVIDIA only

FoveaXR uses variable rate shading: the GPU shades one colour for a block of pixels at the edge of the view instead of one per pixel. In Direct3D 12 this is part of the API itself, as variable rate shading Tier 2, which lets a program set the shading rate with a screen-space image. In Direct3D 11, only NVIDIA offers variable rate shading, through its own driver interface (NVAPI). AMD and Intel drivers have none there. So on an AMD or Intel card, only Direct3D 12 games can be foveated.

Vulkan and OpenGL games are not supported yet.

OpenXR games and OpenVR games

What OpenXR games OpenVR (SteamVR) games
How FoveaXR gets in An OpenXR API layer, registered once Its openvr_api.dll in the game folder, wrapping the original
Setup per game None: every OpenXR game on any runtime, from its next start One Enable click in the Games tab
What a game update does Nothing Replaces FoveaXR’s file; the app shows Re-enable
Undo Uninstall removes the layer Disable or uninstall puts the original file back

The Games tab lists your Steam VR games with their state (On, Off, Updated or Blocked). It can filter by Enabled, OpenVR, OpenXR or Blocked.

Games that are left alone

  • Anti-cheat. FoveaXR never runs in games with EasyAntiCheat or BattlEye, in games on its anti-cheat list, or in VRChat. Do not use it in online games, even where it is not blocked.
  • Games that foveate themselves. These are skipped.

The lists of both kinds of game are in the repository’s profiles/ folder. They are never complete: an issue or a pull request for a game they miss helps.

Games that save nothing

FoveaXR finds a game’s eye images by their render-target size. That works for most games, and fails in three known cases:

  • Games that render the scene at an unusual size.
  • Deferred renderers whose lighting pass binds no depth buffer.
  • Some OpenVR games on Direct3D 12, whose render targets are created before the first frame is sent to SteamVR. FoveaXR does not recognise those targets.

In those games the saving is zero. To check, press Ctrl+F9 in VR to switch foveation off and on; the app then shows the GPU time saved. A game report for a game that saves nothing is as useful as one for a game that saves a lot: the logs show what to teach the detection. Attach the zip from Settings, Export logs.

Linux

The Linux build is experimental and requires more testing.

  • It is for SteamVR on Linux, with games running under Proton.
  • Only Direct3D 12 games can be foveated. Proton turns Direct3D 12’s variable rate shading into Vulkan’s fragment shading rate, so the Vulkan driver must have that feature. This is what FoveaXR’s README expects from the translation layers’ source code; it requires more testing.
  • Direct3D 11 games cannot be foveated under Proton, because Proton’s NVAPI has no Direct3D 11 variable rate shading. The app says so for those games.
  • Each game needs an Enable click with the game closed, OpenXR games included. Start an OpenXR game once first so it has a Proton prefix.

The install guide has the steps.

Edit this page on GitHub