This document will try to explain the nvngx.ini and in-game menu (shortcut key for opening menu is INSERT) settings as much as possible.
OptiScaler supports DirectX 11, DirectX 12 and Vulkan APIs with multiple upscaler backends. You can select which upscaler to use in the [Upscalers] section of the nvngx.ini file.
[Upscalers]
; Select upscaler for Dx11 games
; fsr22 (native dx11), xess (with dx12), fsr21_12 (dx11 with dx12) or fsr22_12 (dx11 with dx12)
; Default (auto) is fsr22
Dx11Upscaler=auto
; Select upscaler for Dx12 games
; xess, fsr21 or fsr22
; Default (auto) is xess
Dx12Upscaler=auto
; Select upscaler for Vulkan games
; fsr21 or fsr22
; Default (auto) is fsr21
VulkanUpscaler=autofsr21means FSR 2.1.2fsr22means FSR 2.2.1xessmeans XeSS
For DirectX11 fsr21_12, fsr22_12 and xess use a DirectX12 background device to be able to use DirectX12 only upscalers. There is a %10-15 performance penalty for this method, but it allows much more upscaler options. Also, the native DirectX11 implementation of FSR 2.2.1 is a backport from the Unity renderer and has it's own problems, some of which are avoided by OptiScaler.
For selecting upscalers from in-game menus Upscalers section could be used.
With OptiScaler 0.4 there are new options for pseudo-supersampling under [Upscalers]
[Upscalers]
; Enable pseudo-supersampling option for Dx12 and Dx11 with Dx12 backends
; true or false - Default (auto) is false
SuperSamplingEnabled=auto
; Pseudo-supersampling ratio
; 0.0 - 5.0 - Default (auto) is 2.5
SuperSamplingMultiplier=autoTo explain it clearly, for example, normally when your game is running at 1080p and Quality is selected as DLSS preset, it would render a 720p image and send it to the upscaler with other necessary input information and generate a 1080p image as output.
If pseudo-supersampling is enabled, it uses SuperSamplingMultiplier to calculate the target render size of the upscaler. For 720p with default multiplier (2.5) it would be 1800p. So now the upscaler will upscale the image to 1800p instead of 1080p, then OmniSaler will downsample the output image to 1080p.
Because of the higher resolution of the upscaled target, there will be a performance loss compared to just upscaling. But subjectively it could produce images close to DLAA quality with higher performance levels.
It can be changed from the in-game menu with real-time results.
For DirectX11 with fsr21_12, fsr22_12 and xess upscaler options, OptiScaler uses a DirectX12 background device to be able to use these DirectX12 only upscalers. This is a very niche feature and can cause issues with unstable GPU drivers (especially on Intel). To mitigate and prevent crashes or graphical issues, this option could be used.
[Dx11withDx12]
; Syncing meathods for Dx11 with Dx12
;
; Valid values are;
; 0 - No syncing (fastest, most prone to errors)
; 1 - Fence
; 2 - Fences + Flush
; 3 - Fences + Event
; 4 - Fences + Flush + Event
; 5 - Query Only
; Default (auto) is 1
TextureSyncMethod=auto
; Default (auto) is 5
CopyBackSyncMethod=auto
; Start output copy back sync after or before Dx12 execution
; true or false - Default (auto) is true
SyncAfterDx12=auto
; Delay some operations during creation of D11wDx12 features to increase compatibility
; true or false - Default (auto) is false
UseDelayedInit=autoThe diagram below shows the flow of Dx11 with Dx12 upscaling process. Yellow circles are sync points (or possible sync points). SyncAfterDx12 selects when the second sync will happen.
No syncing : Self explanotory
Fence : Sync using shared Fences (Signal & Wait). These should happen on GPU which is pretty fast.
Fence + Event : Sync using shared Fences (Signal & Event). Events are waited on CPU which is slower.
Flush : After Signal shared Fence, Flushes Dx11 DeviceContext.
Query Only : Uses Dx11 Query to sync, in general faster that Events but slower than Fences.
When using Events for syncing output SyncAfterDx12=false is usually more performant.
These settings are game and hardware dependent. Default values are set for balanced performance and stable image, for high performance the user might need to tweak them per game.
These can be changed from the in-game menu with real-time results (except UseDelayedInit).
[XeSS]
; Building pipeline for XeSS before init
; true or false - Default (auto) is true
BuildPipelines=auto
;Select XeSS network model
; 0 = KPSS
; 1 = Splat
; 2 = Model 3
; 3 = Model 4
; 4 = Model 5
; 5 = Model 6
;
; Default (auto) is 0
NetworkModel=auto
[CAS]
; Enables CAS sharpening for XeSS
; true or false - Default (auto) is false
Enabled=auto
; Color space conversion for input and output
; Possible values are at the end of the file - Default (auto) is 0
ColorSpaceConversion=autoThe BuildPipelines parameter allows XeSS pipelines to be built during context creation to prevent stuttering later.
NetworkModel is for selecting the network model to be used with XeSS upscaling. (Currently has no visible effect on the upscaled image)
Normally XeSS tends to produce softer final image compared to other upscalers and has no sharpening option to mitigate it. So OptiScaler allows you to use AMD's CAS sharpening filter on the final image to balance upscaled images soft look. CAS is not perfect though, on some games it causes some artifacts/issues like dissapering bloom effects, shifting color tone of the image or causing black screen with no image at all.
- Bloom removed
- Color tone is changed
ColorSpaceConversion to fix color space conversion issues but almost always the default setting would work fine.
It can be changed from the in-game menu with real-time results.
Dump option is for debugging purposes, which would dump input and output parameters and textures for XeSS to game folder.
[FSR]
; 0.0 to 180.0 - Default (auto) is 60.0
VerticalFov=auto
; If vertical fov is not defined will be used to calculate vertical fov
; 0.0 to 180.0 - Default (auto) is off
HorizontalFov=autoTo improve the image quality you can try to match the vertical or horizontal FOV of your game with these settings. The default is 60° vertical FOV and most of the time it works fine.
It can be changed from the in-game menu with real-time results.
DLSS used to have a sharpening option, but later it was removed. So some games have sharpness slider and some do not. With this option you can disable or enable the sharpness of the final image. FSR has built in sharpness but for XeSS CAS option must be enabled.
[Sharpness]
; Override DLSS sharpness paramater with fixed shapness value
; true or false - Default (auto) is false
OverrideSharpness=auto
; Strength of sharpening,
; value range between 0.0 and 1.0 - Default (auto) is 0.3
Sharpness=autoIt can be changed from the in-game menu with real-time results.
OptiScaler provides several options for overriding and locking upscaling ratios.
UpscaleRatioOverride allows you to select a single upscale ratio for all quality presets.
[UpscaleRatio]
; Set this to true to enable the internal resolution override
; true or false - Default (auto) is false
UpscaleRatioOverrideEnabled=auto
; Set this to true to enable limiting DRS max resolution to overriden ratio
; true or false - Default (auto) is false
DrsMaxOverrideEnabled=auto
; Set the forced upscale ratio value
; Default (auto) is 1.3
UpscaleRatioOverrideValue=autoThis can be changed and saved from the in-game menu, but usually the change will take effect after a restart or resolution change.
QualityRatioOverride allows you to override the upscale ratio for each quality preset.
[QualityOverrides]
; Set this to true to enable custom quality mode overrides
; true or false - Default (auto) is false
QualityRatioOverrideEnabled=auto
; Set custom upscaling ratio for each quality mode
;
; Default (auto) values:
; Ultra Quality : 1.3
; Quality : 1.5
; Balanced : 1.7
; Performance : 2.0
; Ultra Performance : 3.0
QualityRatioUltraQuality=auto
QualityRatioQuality=auto
QualityRatioBalanced=auto
QualityRatioPerformance=auto
QualityRatioUltraPerformance=auto**
If both overrides are enabled, the UpscaleRatioOverride has priority over the QualityRatioOverride**
When DrsMaxOverrideEnabled is enabled, it limits the maximum internal rendering resolution to the default rendering resolution instead of the display resolution for DRS supported games. When enabled, it effectively disables DRS. Works with both QualityRatioOverride and UpscaleRatioOverride.
These can be changed and saved from the in-game menu, but usually the change will take effect after a restart or resolution change.
These settings allow you to override the DLSS init flags to fix some issues.
[Depth]
; Force add INVERTED_DEPTH to init flags
; true or false - Default (auto) is DLSS value
DepthInverted=auto
[Color]
; Force add ENABLE_AUTOEXPOSURE to init flags
; Some Unreal Engine games needs this, fixes colors specially in dark areas
; true or false - Default (auto) is DLSS value
AutoExposure=auto
; Force add HDR_INPUT_COLOR to init flags
; true or false - Default (auto) is DLSS value
HDR=auto
[MotionVectors]
; Force add JITTERED_MV flag to init flags
; true or false - Default (auto) is DLSS value
JitterCancellation=auto
; Force add HIGH_RES_MV flag to init flags
; true or false - Default (auto) is DLSS value
DisplayResolution=auto
[Hotfix]
; Force remove RESPONSIVE_PIXEL_MASK from init flags
; true or false - Default (auto) is true
DisableReactiveMask=autoEnabling AutoExposure helps correct problems with dark or washed-out colors.
Enabling HDR has been reported to help with purple hue in some games.
Enabling DisableReactiveMask can help FSR backends in some games, but it usually causes more problems than it solves. That's why it is disabled by default.
Some games may set the motion vector size flag incorrectly, causing excessive motion blur when the camera moves. Enabling or disabling DisplayResolution might help in these situations.
These can be changed from the in-game menu with real-time results.
Some games (especially Unreal Engine) send input resources to DLSS in wrong states, which leads to graphical problems (especially on AMD hardware). Normally OptiScaler tries to detect the engine type and mitigate these problems, but sometimes games do not report this information correctly. To fix problems, these ini parameters would help.
Setting a wrong resource state here can cause a crash!
[Hotfix]
; Color texture resource state to fix for rainbow colors on AMD cards (for mostly UE games)
; For UE engine games on AMD, set it to D3D12_RESOURCE_STATE_RENDER_TARGET (4)
; Default (auto) is state correction disabled
ColorResourceBarrier=auto
; MotionVector texture resource state, from this to D3D12_RESOURCE_STATE_NON_PIXEL_SHADER_RESOURCE (for mostly debugging)
; Default (auto) is state correction disabled
MotionVectorResourceBarrier=auto
; Depth texture resource state, from this D3D12_RESOURCE_STATE_NON_PIXEL_SHADER_RESOURCE (for mostly debugging)
; Default (auto) is state correction disabled
DepthResourceBarrier=auto
; Color mask texture resource state, from this D3D12_RESOURCE_STATE_NON_PIXEL_SHADER_RESOURCE (for mostly debugging)
; Default (auto) is state correction disabled
ColorMaskResourceBarrier=auto
; Exposure texture resource state, from this D3D12_RESOURCE_STATE_NON_PIXEL_SHADER_RESOURCE (for mostly debugging)
; Default (auto) is state correction disabled
ExposureResourceBarrier=auto
; Output texture resource state, from this D3D12_RESOURCE_STATE_UNORDERED_ACCESS (for mostly debugging)
; Default (auto) is state correction disabled
OutputResourceBarrier=autoThese can be changed from the in-game menu with real-time results.
To achieve better texture clarity, MipmapLodBias can be overridden with this setting. -15 is the sharpest and +15 is the fuzziest.
[Hotfix]
; Override mipmap lod bias for textures
; -15.0 - 15.0 - Default (auto) is disabled
MipmapBiasOverride=autoAdjusting MipmapLODBias has an impact on performace!
It can be changed from the in-game menu, needs resolution change to be effective.
This hotfix is based on the original CyberFSR2's restoring ComputeRootSignature logic, I also added the option to restore ComputeRootSignature. I haven't noticed any games that need these options.
[Hotfix]
; Restore last used compute signature after upscaling
; true or false - Default (auto) is false
RestoreComputeSignature=auto
; Restore last used graphics signature after upscaling
; true or false - Default (auto) is false
RestoreGraphicSignature=autoThese can be changed from the in-game menu with real-time results.
[Log]
; Logging
; true or false- Default (auto) is true
LoggingEnabled=auto
; Log file, if undefined log_xess_xxxx.log file in current folder
;LogFile=./CyberXess.log
; Verbosity level of file logs
; 0 = Trace / 1 = Debug / 2 = Info / 3 = Warning / 4 = Error
; Default (auto) is 2 = Info
LogLevel=auto
; Log to console (Log level is always 2 (Info) for performance reasons)
; true or false - Default (auto) is false
LogToConsole=auto
; Log to file
; true or false - Default (auto) is false
LogToFile=auto
; Log to NVNGX API
; true or false - Default (auto) is false
LogToNGX=auto
; Open console window for logs
; true or false - Default (auto) is false
OpenConsole=autoThese can be changed from the in-game menu with real-time results.
[Menu]
; In-game ImGui menu scale
; 1.0 to 2.0 - Default (auto) is 1.0
Scale=autoThese can be changed from the in-game menu with real-time results.
