v1.0.21

Fixed

Correction. The retry below did not do what it says. D3D12_DRED_ENABLEMENT_DISABLED is written nowhere in the add-on, so the second attempt ran under the identical setting and the message announced an action that never happened. Removed in 1.0.24. dred=0 in dlss5-dx11-bridge.cfg is the only thing that produces an attempt without DRED.

• Device creation is retried once with DRED off when the first attempt raises an exception. DRED is switched on immediately before that call and is the only thing this add-on changes ahead of it, so it is taken back out rather than asking anyone to edit a file. Aimed at Prey 2017; the retry path has not run on a machine where device creation succeeds.

Added

• The NVIDIA driver version, alongside the Windows one. Reports carry 32.0.16.1656, discussions use 616.56.
• A warning when the driver is older than the one this release is verified on. Final Fantasy XIV on 560.94 could not create a neural-rendering feature and updating the driver fixed it.
• The denoising capability block reports its result by name and its declared minimum driver. A driver that does not carry the capability key at all is called out: that is what Final Fantasy XIV showed before the update. The minimum shown belongs to Ray Reconstruction and does not speak for neural rendering, which has no capability key of its own.
• Frame timings are marked when the game window is not in focus. An unfocused window changes the frame interval and the bridge's share of it, and the figure then reads as a regression that is not there.

Notes

• D3D12CreateDevice in Prey 2017 carries one hook, ReShade's, with the same bytes after the jump as a title that works. A second injector was ruled out.
• Verified on Baldur's Gate 3 and Final Fantasy XIV.