DLSS 5 Autopilot 2.0.4

Two upstream projects changed shape - DLSS5-Feeder's beta line from
10 September 2026, wilsjo2's OptiScaler fork on 20 September - and took
installs with them.

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.

Fixed

• An OptiScaler install that wrote no OptiScaler (#364). wilsjo2's fork
  published display-filter-v0.2.0-preview on its release page - a separate
  31 MB tool with no OptiScaler.dll in it. "The newest release carrying an
  archive" is what this tool installed from, so that package went into game
  folders: no proxy was written, and the log said "OptiScaler.dll installed
  as dxgi.dll" anyway. A release counts as an OptiScaler release only if it
  carries an OptiScaler package, and an archive with no OptiScaler.dll in
  it is refused before anything in the game folder is touched - naming what
  it did hold. A folder that took that package is marked in the game list,
  and the diagnosis names it instead of sending you after antivirus.
  Install again; what it left behind is on the install record, so uninstall
  takes it with it.
• "Newest release" installed the feeder's beta line (#325, #348).
  DLSS5-Feeder publishes its 1.16 betas with GitHub's pre-release flag
  turned off, so /latest - and everything that follows it - answered
  v1.16.0-beta.x, while this tool's own fallback, which reads the tag,
  answered v0.15.1. Two paths, two answers - and that beta is one of the
  two things that changed on the machine where the video page stopped
  crashing (#325), and the build that could not compile DLSS5_Feed.fx
  (#348). newest release now means the newest release whose tag is not
  a test build, on both paths; newest pre-release, one entry below it
  in feeder build, still takes the betas. An install that landed on a
  beta this way is marked in the game list.

Also

• The checks that watch for this: every build the tool offers has to resolve
  to an OptiScaler package, and the phrases the diagnosis reads are looked
  for in both feeder builds - the stable one and the beta line - instead of
  in whichever one happened to be the default.