v0.12.9 — the classic add-on installs itself when the log reports the driver fault

The classic add-on build now installs itself when a game's log reports the driver fault. (#69)

The Feeder's host measures this and writes the verdict straight into the game's own log:

WARNING: renodx-dlss5 v4.7 with NVIDIA driver 616.64 is a combination measured to fail.
The neural evaluate faults inside the driver's own NGX runtime -- an access violation in
D3D12Core.dll, reached through nvngx_dlssnr.dll -- so DLSS 5 delivers nothing while
everything else keeps working.

v0.12.6 added a tick so you could act on that. But a tick still requires reading a log first, which is the part that does not happen.

Install now reads dlss5-feed.log and host64\dlss5-feed-host.log before fetching anything, and when either carries that verdict it installs renodx-dlss5-4.55 — the build the host names as passing — instead of the newest one. It says so in the install log:

renodx-dlss5-4.55: this game's log reports the newer build faulting in the driver

Ticking the box yourself still wins, and the pin applies to that game only, not to everything you install afterwards.

The trigger is the machine's own measurement, never the driver version number. Upstream measured 616.64 and states that newer drivers are untested — so assuming them would mean downgrading people on no evidence. If your log has never reported the fault, nothing changes.

SHA-256 of dlss5oneclick.exe: 60085e079037e59c9e4eca348465de2f7ac602e8141c0533513722de8df01380