Skip to content

1.0.20

Choose a tag to compare

@NIGos NIGos released this 29 Aug 18:02
· 1 commit to main since this release

Fixed

  • Parameters the game does not set now carry the neutral from nvsdk_ngx_helpers.h. That header never leaves one unset: MV.Scale, DLSS.Pre.Exposure and DLSS.Exposure.Scale all become 1.0, and the subrect bases come from a zeroed struct. Trails beyond the Horizon sets none of them. 1.0.17 invented -1.0 for MV.Scale and reversed every motion vector, which was the smear; 1.0.18 sent nothing and left it to an undocumented default, which was the flicker. Confirmed fixed on Trails beyond the Horizon: the smear and the flicker are both gone.
  • Enabling DRED and creating the D3D12 device are wrapped in exception handlers. Prey 2017 faults inside D3D12Core.dll during device creation. Prey now loses DLSS 5 rather than the game. Aimed at Prey; not verified there.
  • d3dcompiler_47.dll is loaded from System32, not by the default search order, which prefers the game's own copy. The Elder Scrolls Online ships one, and renaming it away is what made ESO work with this add-on loaded. The path taken is logged.

Changed

  • The whole of the DLSS 5 add-on's ReShade.ini section is read, not keys beginning NR. Version 3.3.5 introduced EnableHooks, which decides whether it hooks anything at all.
  • D3D12CreateDevice's prologue is logged before it is called. ReShade hooks that function by design, so a jump there is normal.

Notes

  • ESO with the game's d3dcompiler_47.dll in place is the test this release needs. No renaming should be required.
  • The host-executable hold-back added in 1.0.17 was not what fixed ESO: it was already in force in 1.0.19, which still needed the rename.
  • Verified on Baldur's Gate 3.