Skip to content

gaming:dlss5 — support the DLSS5-Feeder route for games with no upscaler, plus assess fixes from live installs #4592

Closed

Description

@kyle-sexton

Summary

gaming:dlss5 only supports the in-process OptiScaler DLSS-NR route, which needs a game that already calls an
upscaler. Live installs on 2026-09-25/27 (Alien: Isolation, Mass Effect Legendary Edition) show that the
DLSS5-Feeder route (github.com/jlrouzies-fr/DLSS5-Feeder) makes DLSS 5 work in games assess marks
not-a-candidate, and surfaced several assess defects. Everything below was done by hand, so none of it is in a
manifest the skill can status or remove.

Requested: support the Feeder route

  1. Route detection in assess. For a no-upscaler game, report the Feeder route instead of stopping:
    • 32-bit exe: ReShade add-on build (x86) + dlss5-feed.addon32 + host64\ helper (dlss5-feed-host64.exe, a
      64-bit ReShade dxgi.dll, the neural consumer, nvngx_dlssnr.dll, nvngx_dlss.dll). Worked on Alien:
      Isolation with OptiScaler DLSS-NR (wilsjo2 v0.8.3) as host64\winmm.dll.
    • 64-bit exe: ReShade add-on build as dxgi.dll + dlss5-feed.addon64 + consumer in-process. Worked on Mass
      Effect LE (ME1) with renodx-dlss5.addon64 7.0.0-rc8 (RankFTW/rhi-repo release, the Feeder installer's source).
    • Motion-vector provider (LumeniteFX Kernel recommended by the Feeder README, or VORT) + DLSS5_MV_PROVIDER
      preprocessor define + technique order (provider above DLSS5_Feed), plus ReShade.fxh, ReShadeUI.fxh,
      DrawText.fxh, FontAtlas.png (the Feeder's verifier fails without them).
  2. apply / remove / status with a manifest, same byte-exact model as today.
  3. Run the Feeder's own Verify-DLSS5Feeder.ps1 as part of status; it reads dlss5-feed.log and reports
    feature creation, delivered frames, consumer routing, and depth health.

Defects found in assess

  1. No bitness check. Alien: Isolation's AI.exe is PE machine 0x14C (x86). NGX is 64-bit only, so the
    in-process route can never work there; assess should say so.
  2. dx12 flag is wrong both ways. false for The Witcher 3 bin\x64_dx12 (the DX12 build); true for all
    three Mass Effect LE exes, which are D3D11 (imports d3d11/dxgi, no d3d12).

Consumer and compatibility findings

  1. OptiScaler proxy never loaded in ME1, as winmm.dll or version.dll, although the exe imports WINMM.
    Feeder log: "version.dll is an OptiScaler build, but this game never loaded a DLL of that name". renodx-dlss5
    (a ReShade add-on, no proxy name) worked. The consumer needs to be a per-game choice.
  2. Luma + 64-bit Feeder = NGX init crash. Feeder log: "NVSDK_NGX_D3D12_Init raised exception 0xC0000005
    (caught) in Luma-Mass Effect Legendary Edition.addon". Luma's documented Feeder success (BioShock Remastered)
    is 32-bit, where NGX runs in the separate helper. assess should flag a Luma add-on on the 64-bit route and
    suggest RenoDX HDR instead (what worked here: renodx-masseffectle.addon64, snapshot 2026-09-22).
  3. Depth on the wrong buffer is common and silent: "depth is FLAT while the scene moves: ReShade's Generic Depth
    is on the wrong buffer". Surface it after the first launch.
  4. renodx-dlss5 settings reference (ranges from the Feeder's panel mirror, src/dlss5-feed32.cpp kNR):
    Style 0-2 (Default/Natural/Cinematic; NRStyle=2 crashes the next boot per the README), Skin Structure -1..1,
    Color Strength 0..1, Transfer Strength 0..1, Intensity 0..2. These differ from OptiScaler DLSS-NR's ranges, so a
    preset format must be per-consumer. v4.6/v4.7 fail on drivers 616.64+; 6.1/7.0.0-rc8/8.0.1 pass the helper
    self-test per the Feeder 1.17.0-beta.3 notes.

Anti-cheat (worked correctly, keep)

  • Helldivers 2: signals (nProtect GameGuard via AreWeAntiCheatYet and the Steam store), acknowledgement required.
  • Halo MCC: signals (Easy Anti-Cheat on disk and in AreWeAntiCheatYet).
  • The Feeder route does not lower anti-cheat risk: it needs ReShade's unsigned add-on build, and ReShade disables
    depth in multiplayer. Keep the same gate for it.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Sep 27, 2026
  2. kyle-sexton commented on Sep 27, 2026

    @kyle-sexton
    MemberAuthor

    This was generated by AI during triage.

    Triage: briefed, human-gated

    Category: enhancement (new install route) with two bundled assess defects. Type: Feature. priority: medium (assessed default; nothing blocked, no deadline).

    Verified against main (read-only)

    • Bitness (item 4): confirmed. assess performs no PE machine check, and the skill's candidate-selection reference says so explicitly ("assess does not test for one"). A 32-bit exe cannot host the 64-bit-only NGX in-process route.
    • dx12 flag (item 5): confirmed plausible both ways. The flag is a heuristic: true when a d3d12*.dll sits beside the exe OR the path ends in Binaries\Win64 (the Unreal layout). That makes any Unreal-layout D3D11 game read true (Mass Effect LE) and any DX12 game that ships no local d3d12*.dll read false (Witcher 3 bin\x64_dx12). Reading the exe's import table would settle both.
    • Feeder route (items 1-3, 6-9): not reproducible here (Windows + GPU + game installs); taken as the reporter's live-install evidence.

    Why human-gated

    • Supply-chain and scope decision. The Feeder route installs a third-party loader chain (DLSS5-Feeder, ReShade's unsigned add-on build, a 64-bit helper, a motion-vector shader provider, per-game consumers such as renodx-dlss5 or an OptiScaler DLSS-NR proxy). Whether this plugin adopts, pins, and attests those artifacts is a maintainer policy call, the same kind the existing fork-comparison and hash-attestation records make for OptiScaler.
    • Design space still open. Per-game consumer choice (item 6), a per-consumer preset format (item 9), and the Luma-on-64-bit refusal (item 7) change the manifest and preset model; they need a decided shape before an agent builds them.

    Recommended next step

    Run /work-items:decompose on this item:

    1. Slice A (small, can go first): assess reports exe bitness and derives dx12 from the exe's imports rather than folder heuristics; a 32-bit exe is reported as incompatible with the in-process route. Acceptance: Alien: Isolation (x86) flagged; Witcher 3 DX12 build dx12: true; Mass Effect LE exes dx12: false.
    2. Slice B (after the policy decision): Feeder route detection in assess, then apply/remove/status with a byte-exact manifest, then Verify-DLSS5Feeder.ps1 in status, then consumer/compatibility checks (items 6-8), then per-consumer presets (item 9).
    3. Keep the anti-cheat gate unchanged for the Feeder route, as the item says.

    Decision for the maintainer: adopt the Feeder route (and which artifacts to pin), or scope this item down to the assess fixes only.

  3. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Sep 27, 2026
  4. kyle-sexton commented on Sep 29, 2026

    @kyle-sexton
    MemberAuthor

    Reopening. This item was closed by PR #4911 (Closes #4592) by mistake.

    Decision needed. Adopt the DLSS5-Feeder route into gaming:dlss5, or scope this item down to the assess fixes already shipped?

    • A) Adopt. Decide which artifacts to pin and attest (DLSS5-Feeder release or commit, ReShade unsigned add-on build, host64 helper, motion-vector provider, per-game consumers), then run /work-items:decompose into a slice for detection, apply/remove/status with manifest, verifier in status, consumer checks, and per-consumer presets. The anti-cheat gate applies unchanged.
    • B) Scope down. Remove the Feeder pointers from SKILL.md, candidate-selection.md and feeder-route.md, close this item as delivered by feat(gaming): read dlss5 assess bitness and dx12 from PE tables (Refs #4592) #4646, no follow-up.
    • C) Keep documentation-only. Leave feeder-route.md as unverified operator guidance behind the anti-cheat gate and file no build work.

    RECOMMENDED (AI recommendation, not a decision): B or C over A for now. Basis: the 2026-09-27 triage comment calls this a supply-chain and scope decision; the route installs an unsigned ReShade add-on chain that raises anti-cheat risk; nothing is pinned or attested; the Feeder items were "not reproducible here" (a single reporter's live installs); upstream was never fetched before #4911.

    Unblocks: A releases the undelivered items for the work loop. B or C lets the three #4592 pointers in the docs be removed or retargeted.

    Meanwhile: draft PR #5238 is docs-only and decision-neutral. It restores the anti-cheat gate on the Feeder mention, makes the 32-bit text consistent, removes a stale bullet, adds a verification record and evals. It uses Refs #4592 and leaves this item open. No option is implemented.

  5. kyle-sexton commented on Sep 29, 2026

    @kyle-sexton
    MemberAuthor

    Reopened: the merge of #5238 auto-closed this issue because the PR body's prose "...added and closed #4592 for" matched a GitHub closing keyword. #5238 implements neither option; the owner decision in the packet above is still open.

  6. kyle-sexton commented on Sep 29, 2026

    @kyle-sexton
    MemberAuthor

    Owner decision (2026-09-29): Option B, scope down. Remove the Feeder pointers from SKILL.md, candidate-selection.md and feeder-route.md, and treat the issue as delivered by #4646 (items 4-5). Owner's note: option C (keep documentation-only, unverified operator guidance behind the anti-cheat gate, no build work) is also acceptable. Items 1-3 and 6-9 are not built and no follow-up is filed.

    Next: an agent removes the Feeder pointers in a draft PR that closes this issue; the issue stays open until that PR merges.

  7. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    needs-owner-decisionAwaiting a human or maintainer judgment call.
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.

    Fields

    No fields configured for Feature.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions