You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DLSS render preset is copied to the D3D12 feature. All six DLSS.Hint.Render.Preset.* keys are mirrored when the game sets them. The preset selects which DLSS model runs, so the two sides were upscaling with different models and the neural-rendering add-on worked from the D3D12 one. Prey 2017 reaches DLSS through Luma, which sets these; DLSSTweaks, OptiScaler and many games set them directly. Unlike MV.Scale, nvsdk_ngx_helpers.h does not write these keys, so an absent one is left absent rather than given a value.
Added
A module that exports the NGX entry points but is not the driver's loader is named when the D3D12 session faults. Prey 2017 runs OptiScaler installed as WINMM.dll: it patches code inside the driver's NGX module and opens its own session on it first, which is the difference from titles where the same driver and module initialise. The log now says so and names the test — running without the proxy.
Notes
Baldur's Gate 3 sets no render presets and loads no NGX proxy, so both additions were verified only in that they stay silent. Neither has been seen doing its work.
Prey 2017 on 1.0.22 takes the correct NGX module and still faults in Init_Ext. The module choice fixed in 1.0.22 was a real defect but not the cause there. The SDK version is ruled out: Baldur's Gate 3 initialises with the same version, driver and module.