Add FidelityFX SuperResolution to SteamVR games

On Pimax headsets the radius setting seems to be inverted, causing the use of bilinear upscaling in the sweetspot of the lens while fsr is applied outside of the specified radius. Disabling the radius (setting radius to 2) appears to function as intended however. This seems to be the case regardless of fovated rendering. I set the sharpening to 1, radius to 0.6, and renderScale to 0.77 to highlight the effect I'm talking about.

This is an anotated screenshot of the steamvr headset view of the right eye.

This is a screenshot taken by steamvr.

Here's my log if it helps.

openvr_mod.log

Both Euro and American truck simulator does not work,

VR mode starts and work fine, but FSR is not doing anything, this is the log i got for both

Initializing hooks...
Requested interface FnTable:IVRSystem_021
Requested interface FnTable:IVRCompositor_026
Shutting down hooks.

Other than Skyrim and Fallout 4 , all of the games I've tried PCars2 , Dİrt Rally, Half-life Alyx (which gives error if dll is changed) only Pavlov works with this, I can see it working ingame and also got the log on the dll directory. Is this normal at this moment ?

Thanks for your work - I know it's only meant for some specific games, however:

I gave it a spin in IL2 Sturmovik using an HP Reverb G2 and although the game loads fine and FSR is doing its thing, there seems to be some sort of problem in the projection of the image - looks like the images on the screens are too wide-apart or something and there seems to be some slight distortion when pitching the view.

Any tips on what to check on correcting this?

Hi FHolger

can you please enable the wiki of this project to document all tested games?

for example:

Game|Engine|dll location|extra notes|tested down to ---|---|---|---|--- Project Wingman|Unreal 4|%steam app / common% /Project Wingman/Engine/Binaries/ThirdParty/OpenVR/OpenVRv1_5_17/Win64/ |below balanced "small" text is unreadable|rx 480 DCS World|Custom?|%steam app / common% /DCSWorld/bin/ |below quality UI text is unreadable|rx 480

I've applied this mod to Hellblade VR and the resolution scaling doesn't seem to work. The sharpening seems to do something because image looks to be a little sharper but performance is slightly worse than it would be without the mod by about 10FPS on my system.

so this mod is awesome and I would really love it to work with Revive and it does work to an extent i.e. if I replace the openvr_api32/64 dlls with the one from this mod it technically works but for some reason the games are super dark and unplayable.

have tested with Lone Echo and Stormland and get the same issue.

would be awesome if this worked as i could finally play these games without having to turn everything to LOW , and with the mod enabled I get playable FPS at higher settings. it's just too dark to enjoy them.

have tried fiddling with brightness settings in steamvr and using things like FPSVR but nothing works

I've just updated to RC1 and it appears to have affected the brightness/gamma in DCS 2.7.3 Open Beta. The image is now very bright. This seems to be the opposite of issue #10 sadly.

The image looks normal/as expected in the mirror. I faked up some images which I can attach if you want, but "looks too bright" really does cover it.

(Excellent work, btw. Thank you!)

I have tried the mod in Dirt 2 and it works but the dashboard of the car leaves it very dark and I have tried various sharpness values ​​but nothing varies. Without the same car and circuit mod, the dashboard looks much brighter and looks perfectly. Do you know why it can be?

Hello!

I've been having some difficulty getting this to run properly (using an RTX 3080 and Index). I'm convinced the DLL is working, because the "renderScale" value in the config is affecting the output resolution, although FSR does not appear to be occuring at all. (wasn't seeing anything weird in the log file either)

I've tried messing with the radius setting, and I've been unable to destinguish any difference between the center and edges of the image (even when looking at it in the deskop view), it all just looks low resolution.

I've tested this with Revive (by swapping it's DLL instead of a specific game), and in a basic example with Beat Saber, and have gotten the same results.

Is it possible I'm doing something wrong, or maybe just over thinking how good FSR should look? So far it's just looked identical as if I were to just run at that resolution.

Thanks!

AMS2 works excellently with full detail via the Oculus Link with the AMD 6900XT and a 5800X ..... 90 FPS without problems (0.77 FSR). When I try to play wirelessly via Virtual Desktop, I get an error message.

Thanks for the MOD :-D

I try this version v2.1.1 and install it to the latest version of vtol vr game folder, it's working the graphic changed, but the problem is that I can't press any button on my quest 2 controllers the trigger also doesn't work

{ "fsr": { // enable image upscaling through AMD's FSR or NVIDIA's NIS "enabled": true,

// if enabled, uses NVIDIA's Image Scaling instead of the default
// AMD FidelityFX SuperResolution. Both algorithms work similarly, but produce
// somewhat different results. You may want to experiment switching between the
// two to determine which one you like better for a particular game.
"useNIS": false,

// Per-dimension render scale. If <1, will lower the game's render resolution
// accordingly and afterwards upscale to the "native" resolution set in SteamVR.
// If >1, the game will render at its "native" resolution, and afterwards the
// image is upscaled to a higher resolution as per the given value.
// If =1, effectively disables upsampling, but you'll still get the sharpening stage.
// AMD presets:
//   Ultra Quality => 0.77
//   Quality       => 0.67
//   Balanced      => 0.59
//   Performance   => 0.50
"renderScale": 0.77,

// tune sharpness, values range from 0 to 1
"sharpness": 0.9,

// Only apply FSR/NIS to the given radius around the center of the image.
// Anything outside this radius is upscaled by simple bilinear filtering,
// which is cheaper and thus saves a bit of performance. Due to the design
// of current HMD lenses, you can experiment with fairly small radii and may
// still not see a noticeable difference.
// Sensible values probably lie somewhere between [0.2, 1.0]. However, note
// that, since the image is not spheric, even a value of 1.0 technically still
// skips some pixels in the corner of the image, so if you want to completely
// disable this optimization, you can choose a value of 2.
// IMPORTANT: if you face issues like the view appearing offset or mismatched
// between the eyes, turn this optimization off by setting the value to 2.0
"radius": 0.5,

// if enabled, applies a negative LOD bias to texture MIP levels
// should theoretically improve texture detail in the upscaled image
// IMPORTANT: if you experience issues with rendering like disappearing
// textures or strange patterns in the rendering, try turning this off
// by setting the value to false.
"applyMIPBias": true,

// If enabled, will visualize the radius to which FSR/NIS is applied.
// Will also periodically log the GPU cost for applying FSR/NIS in the
// current configuration.
"debugMode": false,

"hotkeys": {
  // If enabled, you can change certain settings of the mod on the fly by
  // pressing certain hotkeys. Good to see the visual difference. But you
  // may want to turn off hotkeys during regular play to prevent them from
  // interfering with game hotkeys.
  "enabled": true,

  // if enabled, must also be holding CTRL key to use hotkeys
  "requireCtrl": false,

  // if enabled, must also be holding ALT key to use hotkeys
  "requireAlt": false,

  // if enabled, must also be holding SHIFT key to use hotkeys
  "requireShift": false,

  // Below, you can see what hotkey functions are available and also configure
  // the hotkey for it. To configure the hotkey, you need to use the corresponding
  // virtual key code, which you can look up on this page:
  // https://cherrytree.at/misc/vk.htm

  // switch between FSR and NIS (default key: F1 - 112)
  "toggleUseNIS": 112,

  // toggle debug mode on or off (default key: F2 - 113)
  "toggleDebugMode": 113,

  // decrease sharpness by 0.05 (default key: F3 - 114)
  "decreaseSharpness": 114,

  // increase sharpness by 0.05 (default key: F4 - 115)
  "increaseSharpness": 115,

  // decrease sharpening radius by 0.05 (default key: F5 - 116)
  "decreaseRadius": 116,

  // increase sharpening radius by 0.05 (default key: F6 - 117)
  "increaseRadius": 117,

  // take a screenshot of the final output sent to the HMD (default key: F7 - 118)
  "captureOutput": 118
}

} }

Plugin Fehlermeldung! Was soll ich jetzt machen? Die Log-Datei ist nicht vorhanden. Es liegen auch 2 Dateien, aber mit unterschiedlichem Datum vor. Eine Datei vom 17.01.2022 und eine Datei vom 26.12.2021 vor. Ich weiß nicht warum.

Danke für die Hilfe.

Plugin error message! What should I do now? The log file does not exist. There are also 2 files, but with different date. A file from 17.01.2022 and a file from 26.12.2021 are present. I do not know why.

Thanks for the help.

{ "foveated": { // enable fixed foveated rendering "enabled": true,

// if enabled, will attempt to use variable rate shading
// NOTE: only works on NVIDIA RTX or GTX 16xx cards!
"useVariableRateShading": true,

"innerRadius": 0.6,
"midRadius": 0.8,
"outerRadius": 1.0,

"sharpen": {
    // sharpen the image with NVIDIA's NIS sharpening
    "enabled": true,

    // tune sharpness, values range from 0 to 1
    "sharpness": 0.4,
    
    // Only apply sharpening to the given radius around the center of the image.
    // Saves a bit of performance.
    "radius": 0.75
},

// If enabled, will visualize the radius to which sharpening is applied.
// Will also periodically log the GPU cost for image restore and sharpening in the
// current configuration.
"debugMode": false,

"hotkeys": {
  // If enabled, you can change certain settings of the mod on the fly by
  // pressing certain hotkeys. Good to see the visual difference. But you
  // may want to turn off hotkeys during regular play to prevent them from
  // interfering with game hotkeys.
  "enabled": true,

  // if enabled, must also be holding CTRL key to use hotkeys
  "requireCtrl": false,

  // if enabled, must also be holding ALT key to use hotkeys
  "requireAlt": false,

  // if enabled, must also be holding SHIFT key to use hotkeys
  "requireShift": false,

  // Below, you can see what hotkey functions are available and also configure
  // the hotkey for it. To configure the hotkey, you need to use the corresponding
  // virtual key code, which you can look up on this page:
  // https://cherrytree.at/misc/vk.htm

  // toggle fixed foveated rendering on or off (default key: F1 - 112)
  "toggleFFR": 112,

  // toggle debug mode on or off (default key: F2 - 113)
  "toggleDebugMode": 113,

  // decrease sharpness by 0.05 (default key: F3 - 114)
  "decreaseSharpness": 114,

  // increase sharpness by 0.05 (default key: F4 - 115)
  "increaseSharpness": 115,

  // decrease currently selected radius by 0.05 (default key: F5 - 116)
  "decreaseRadius": 116,

  // increase currently selected radius by 0.05 (default key: F6 - 117)
  "increaseRadius": 117,

  // select the inner FFR radius for manipulation (default key: 1 - 49)
  "selectInnerRadius": 49,

  // select the middle FFR radius for manipulation (default key: 2 - 50)
  "selectMidRadius": 50,

  // select the outer FFR radius for manipulation (default key: 3 - 51)
  "selectOuterRadius": 51,

  // select the sharpening radius for manipulation (default key: 4 - 52)
  "selectSharpenRadius": 52,

  // take a screenshot of the final output sent to the HMD (default key: F7 - 118)
  "captureOutput": 118,

  // toggle between variable rate shading (VRS) and radial density masking (RDM)
  // (default key: F8 - 119)
  "toggleUseVRS": 119
}

} }

whenever i use FSR on a game the up scaling and graphics work but i cant control my character or have it tracked i just float randomly in the air in front of the character with my head locked please help

I've tried to add the mod to Bonelabs, but I somehow can't find the "openvr_api.dll" file.

Am I just blind or is there something different with Bonelabs?

Thanks Guys!