OptiScaler + DLSS Neural Rendering v0.2.0 #17
Replies: 6 comments 1 reply
|
Hey, please drop all of your issues here. I will focus on them for the next couple of days until I get OptiScaler + DLSSNR up to par with my expectations. Then I'll start adding bigger features. Expect multiple releases a day, they will be set as a pre-release if not too important, after some patches have been out I'll drop a new latest release that is a collection of all the patches that I released earlier. |
|
Hello, Quick question, what’s the best way to update to the new version? Should I delete the old build first then install the new one, or just overwrite the existing files? I’d like to keep my custom settings if possible and make the update as simple as I can. Thanks. |
|
Hello, how can I change The reversible proxy (Colour → "Reversible proxy") settings from .ini file? I am playing gta v enhanced and it is impossible to save the settings while inside the game. I tried the DirectStorageFix and giving permissions to gta folder but no luck. Thank You!!!!! |
|
Does this currently support linux? |
|
so we need to enable " The exposure scan is opt-in " to use it in games when Opti doesnt find an exposure value to work with ? |
|
I am trying to use OptiScaler + DLSS Neural Rendering v0.2.0 but it won’t recognize DLSSG output. Keeps asking if I’m missing streamline even though it is located in it's place. |
|
I successfully enabled DLSS NR in Assassin's Creed Origins using DLSS Enabler combined with ReShade (renamed to reshade64.dll, loading ACOrigins-DLSS.addon64 via OptiScaler), but the built-in FG OUTPUT doesn't work. Is it true that OptiScaler FG itself simply cannot run on DX11? When I turn it on, the game works, but the screen is black. [W] CheckForFGStatus FGOutput doesn't have any FG active |
Uh oh!
There was an error while loading. Please reload this page.
OptiScaler + DLSSNR v0.2.0
This bundles a ton of improvements ranging from bugs and crash fixes, and UI improvements to additional color correction methods and improved quality for those who are willing to trade a bit of performance for higher sharpness and less noise.
The "replace" proxy are known to cause issues on certain games, the issues look like flashing lights or even no lights where there should be.
The color strength slider is supports now values way too high than frankly nobody should be using, but this could be used as an atmosphere so keeping it. Be aware it could cause flickering when set to high.
The next couple updates will come as patches, so quick fixes. This means they'll come fast, maybe multiple times day. More significant updates will still be worked on and released.
What is it ?
OptiScaler with an extra pass: NVIDIA's Neural Rendering model (DLSS5), run over the upscaler's output
to synthesise detail. NVIDIA ships no public integration for it, so it is driven directly. Nothing here
is officially supported and none of it is documented by NVIDIA.
v0.2.0 is a colour-and-control release. The big one is a new proxy that stops the model being starved
in highlights, so it actually has detail to enhance where the old curve handed it flat white. On top of
that: multi-point exposure calibration so the white point holds as the light changes, a frame-hold mode
for comparing settings honestly, and a set of native Vulkan crash fixes. It also lets you run the model
above native, so supersampling it, then averaging the result back down for a cleaner, less noisy pass. Further more, thanks to hhkbble's contribution, it now reads the game's own exposure live, so the white point no longer lags a scene change.
What you need
modded nvngx_dlssnr.dll.
Vulkan is supported natively; DX11 runs through the bridge, which now supports DLSS directly.
Install
will load and writes an uninstaller.
You can bind a key to it under Keybinds, "Neural Rendering" — unbound by default — to flick the pass on
and off without opening the menu.
About the model DLL
nvngx_dlssnr.dll is not in this archive and will not be. It is NVIDIA's, not mine to redistribute, and
requests for it will not be answered. It comes from a driver package, and you need one copy in each game
folder. There is no shared or system-wide location.
The forwarder that ships here (nvngx.dll_dlssnr.dll) is not the model. It exists only because the model
refuses calls from any module whose path does not contain nvngx.dll, so the forwarder is named to
satisfy that check.
Credit
The colour composition — how the model's answer is brought back into your frame — is taken from RenoDX's
DLSS 5 addon by clshortfuse (github.com/clshortfuse/renodx), used under its MIT licence. It is their
design and the reason the colour holds together. The new reversible proxy in this release is also
adapted from RenoDX's later work. See Licenses/RenoDX_ATTRIBUTION.txt.
Two ideas for running the model below native resolution come from hhkbble, from their pull request
against this fork: an exact-area box-filter downsample (so less aliasing reaches the model) and the
matched residual (lay only the model's low-res difference on the frame's own full-res proxy, instead
of composing a small picture against a large one). Both are selectable under Enlargement.
Removing it
Run the uninstaller setup_windows.bat wrote, or delete the files you extracted. Setting Enabled=false
under [DlssNr] in OptiScaler.ini turns off the pass while leaving OptiScaler working normally.
Reporting problems
Include OptiScaler.log, your GPU and driver version, the game, and whether Ray Reconstruction and frame
generation were on. File logging is off by default — set
LogToFile=trueunder [Log] inOptiScaler.ini before capturing a log. Issues is for clear, reproducible bugs; if you are unsure, use
Discussions.
How the new features work
The reversible proxy (Colour → "Reversible proxy")
The model is never shown your frame directly. It is shown a tone-mapped proxy of it, and its answer is
transferred back. The old proxy (a soft knee) rolls highlights off so hard that a surface twice as bright
as white and one four times as bright arrive almost identical, so the model sees flat white and has
nothing to enhance there. The bright parts come back with light but no detail.
The reversible proxy uses an unclipped curve instead, where those same two land far apart, so the model
sees gradation everywhere and can actually work on it. Five settings:
strength, highlight guard, palette). It wins in bright scenes, but the curve compresses midtones too,
so in soft-lit content it can be worse than Off, and it shifts the effective paper white (re-check
paper white when you switch to it).
reference; gorgeous where there are no bright lights, but they flash in motion. A lever, not a setting.
(as good as Off there) and the unclipped roll only in the highlights, so it recovers the detail Off
crushes without giving up the midtones Neutwo does. It barely shifts paper white.
confined to genuinely bright highlights instead of everywhere. Most of Replace's detail, far more
stable. If you love the Replace look but the flicker bothers you, this is the one.
Multi-point exposure anchoring (white point → "a buffer the scan found")
When the white point is driven by a scanned buffer, one calibration point is only correct near the
lighting where you set it, and drifts as the scene gets much brighter or darker. Now you can place
several: set paper white until a scene looks right and press Anchor, move to very different light and
do it again. The white point is interpolated between your points, so it holds across the whole range.
Click a row to fine-tune that point; × deletes it. One point behaves exactly as before, and the whole
table is saved per game.
Frame hold (Compare → "Hold frame")
Comparing two settings is impossible while the scene keeps moving. Hold frame freezes the frame the model
works on; while it is held, change paper white, the strengths, the reversible mode or the model preset,
and only that setting moves — the scene does not. Hide the menu and it stays held; untoggle to resume.
It cannot show upstream changes (DLSS/FSR/XeSS presets — the upscaler is not re-run on a held frame) or
freeze the game's own HUD and post-processing, and the white point holds its value while frozen.
While a frame is held you can also switch Apply the model off: the pass keeps running but outputs
the clean frame, so you see the same frozen frame with and without Neural Rendering. The cost readout
stays honest about it — "model running, edit hidden" — because the model is still doing its work.
Supersampling the model (Model resolution above 100%)
The model-resolution slider now goes past 100%. Above native the model runs supersampled — on a larger,
cleaner input — and its answer is averaged back down to your frame with a real downscaler (Lanczos and
friends, chosen in the dropdown that appears above 100%). A single-tap shrink would only alias the
model's detail back into noise; a proper area filter turns the extra resolution into less noise
instead. It is costly — the model's time grows with the area — so it is a quality lever for when you
have the headroom, capped at 2×. Works on DX12 and native Vulkan, and its downscaler is independent of
Output Scaling's, so you can supersample the model and downscale the whole frame at once.
Live exposure (white point → "the game's own exposure")
When the white point follows the game's exposure it used to arrive a few frames late — read back from
the GPU a beat behind the scene. It is now read inside the pass, the same frame, so a cut from dark to
bright no longer drags the white point behind it. DX12; if the exposure ever reads back wrong it falls
to the value it always used, so nothing regresses.
CHANGELOG (since v0.1.2)
New
Five modes (default Off): Off, Neutwo composed, Neutwo replace, Hybrid composed — the
recommended best-of-both (soft-knee midtones + unclipped highlights) — and Hybrid replace (raw
detail with the flashing confined to real highlights). (Colour section.)
conditions; it interpolates between them and holds across the range. Saved per game.
model" can be switched off while held to see the same frozen frame with and without the pass.
its answer back down with a downscaler of your choice, for a cleaner, less noisy pass. DX12 and
native Vulkan; the NR downscaler is independent of Output Scaling's, so both can run at once.
in-pass every frame instead of a few frames late, so it tracks scene changes without lag. (DX12.)
flat peaks; it rolls off at the edge of the gamut instead of blowing out.
DirectX 12, for Vulkan games that compute an exposure but never hand it to the upscaler. Opt-in and
experimental, like the DirectX 12 scan.
and "a buffer the scan found" green when they have real data and orange when they don't, so the
right source is obvious before you open it. Paper white stays neutral — it always works.
Improved (arrived across v0.1.3 → v0.2.0)
guard, and hue kept through the knee.
Enlargement.
Fixed
RDR2, Enshrouded) — a mid-flight resize freed resources still in use; it now drains first.
device; they are now abandoned safely.
UAV; it now reads the real state, so an FSR/XeSS title with a per-game barrier override is safe.
titles (e.g. Cyberpunk 2077): the scan pinned a driver-owned resource whose memory was freed at
feature teardown. It now releases its references first.
Experimental / known limits and issues
upscaler to DLSS and choose your real upscaler with
VulkanUpscalerin the ini (e.g.ffxforFSR) — selecting the game's own FSR/XeSS often isn't intercepted on Vulkan. Also, the
_12(bridged)Vulkan backends run the pass on D3D12, so the exposure scan can't reach a Vulkan game's exposure
there — use a native backend (
ffx,dlss,xess) if you want the scan.titles (e.g. Cyberpunk 2077) compute exposure in a form the scan cannot see, in which case the white
point falls back to the paper-white slider. This is a limitation, not a fault: the scan is only a
fallback for games that do not hand their exposure to the upscaler.
This discussion was created from the release OptiScaler + DLSS Neural Rendering v0.2.0.
All reactions