DLSS 5 Autopilot 2.0.8

Updating from 2.0.x with update now downloads this build, checks its
SHA-256 against the SHA256SUMS.txt published with the release, and offers
a one-click restart. Your settings, library, hidden games and profiles carry
over.

Added

• did it work? reads DLSS5-Feeder 1.18.0-beta.1's lines. When NGX refuses
  to create DLSS, the beta logs NGX's own result, and the verdict names it.
  When the feeder itself says NGX would not set DLSS up inside the game's
  process, the verdict says so and points to another route. Both feeder
  add-ons in one folder (dlss5-feed.addon64 and
  dlss5-feed-helper.addon64) is named as its own fault. The default feeder
  build is still the newest stable feeder release; the beta is newest
  pre-release under feeder build. These lines were read from the
  beta's files; the beta has not been run on this tool's test machine.
• The Remix route reads the swapped runtime's log. The runtime the swap
  installs (lunks/dxvk-remix-plus-dlssnr) logs its neural frames in its own
  words, and none of them were read: every session with a log came back
  "the neural pass was never even attempted" and was shared as not
  working. Evaluated frames read as working, and a failure shows NGX's
  reason. A pass switched
  off, or a log with no neural line, is not filed as failed: share the
  result asks you what happened instead.
  These lines were read from the runtime's files; it has not been run on
  this tool's test machine.
• The OptiScaler route asks what the game loaded. With no OptiScaler
  log, did it work? reads which DLLs the game had loaded when the tool
  looked. A proxy the game had not loaded is named, with the fix: another
  name under loads as. A game that ran from another folder is named
  too, with both folders.

Fixed

• A Remix log from before the install was read as "Remix ran". It counts as
  no log at all.
• report a bug carried the last 100 KB of OptiScaler.log and of
  dlss5-feed.log, while the check read 400 KB. After a flood of errors the
  lines that decided the verdict were missing from the report (#580). Both
  read the same amount, and the report takes OptiScaler's last run only, as
  the check does.
• A game that ran from another executable, or whose proxy name it does not
  load, no longer makes the watcher suggest another route: the fix is on
  the same route, and a shared result no longer counts it as that route
  failing.
• The watcher's messages name the next route as the route list does
  (standalone-dlssnr, neural-upstream, renodx-dlss).
• The Remix runtime swap says where it has been run: its author reports it
  running in Portal with RTX; it has not been run on this tool's test
  machine.