Repository navigation
Closed
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.
Description
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
- 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 ReShadedxgi.dll, the neural consumer,nvngx_dlssnr.dll,nvngx_dlss.dll). Worked on Alien:
Isolation with OptiScaler DLSS-NR (wilsjo2 v0.8.3) ashost64\winmm.dll. - 64-bit exe: ReShade add-on build as
dxgi.dll+dlss5-feed.addon64+ consumer in-process. Worked on Mass
Effect LE (ME1) withrenodx-dlss5.addon647.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 aboveDLSS5_Feed), plusReShade.fxh,ReShadeUI.fxh,
DrawText.fxh,FontAtlas.png(the Feeder's verifier fails without them).
- 32-bit exe: ReShade add-on build (x86) +
- apply / remove / status with a manifest, same byte-exact model as today.
- Run the Feeder's own
Verify-DLSS5Feeder.ps1as part ofstatus; it readsdlss5-feed.logand reports
feature creation, delivered frames, consumer routing, and depth health.
Defects found in assess
- No bitness check. Alien: Isolation's
AI.exeis PE machine0x14C(x86). NGX is 64-bit only, so the
in-process route can never work there;assessshould say so. dx12flag is wrong both ways.falsefor The Witcher 3bin\x64_dx12(the DX12 build);truefor all
three Mass Effect LE exes, which are D3D11 (imports d3d11/dxgi, no d3d12).
Consumer and compatibility findings
- OptiScaler proxy never loaded in ME1, as
winmm.dllorversion.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. - 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.assessshould 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). - 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. - renodx-dlss5 settings reference (ranges from the Feeder's panel mirror,
src/dlss5-feed32.cppkNR):
Style 0-2 (Default/Natural/Cinematic;NRStyle=2crashes 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.
Metadata
Metadata
Assignees
Labels
agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.
Type
Fields
No fields configured for Feature.
Activity
kyle-sexton commentedon Sep 27, 2026
This was generated by AI during triage.
Triage: briefed, human-gated
Category: enhancement (new install route) with two bundled
assessdefects. Type: Feature.priority: medium(assessed default; nothing blocked, no deadline).Verified against
main(read-only)assessperforms no PE machine check, and the skill's candidate-selection reference says so explicitly ("assessdoes not test for one"). A 32-bit exe cannot host the 64-bit-only NGX in-process route.dx12flag (item 5): confirmed plausible both ways. The flag is a heuristic: true when ad3d12*.dllsits beside the exe OR the path ends inBinaries\Win64(the Unreal layout). That makes any Unreal-layout D3D11 game readtrue(Mass Effect LE) and any DX12 game that ships no locald3d12*.dllreadfalse(Witcher 3bin\x64_dx12). Reading the exe's import table would settle both.Why human-gated
Recommended next step
Run
/work-items:decomposeon this item:assessreports exe bitness and derivesdx12from 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 builddx12: true; Mass Effect LE exesdx12: false.assess, then apply/remove/status with a byte-exact manifest, thenVerify-DLSS5Feeder.ps1instatus, then consumer/compatibility checks (items 6-8), then per-consumer presets (item 9).Decision for the maintainer: adopt the Feeder route (and which artifacts to pin), or scope this item down to the
assessfixes only.feat(gaming): read dlss5 assess bitness and dx12 from the exe's PE ta…
ci(test-windows): run the gaming dlss5 selftest on windows-2025
test(gaming): rename the PE fixture builder's name helper
fix(gaming): restore upstream files a stale index dropped
feat(gaming): read dlss5 assess bitness and dx12 from PE tables (Refs #…
docs(gaming): park DLSS5-Feeder research (#4592) (#4911)
docs(gaming): add a four-part verification record to the Feeder route…
test(gaming): cover the gated Feeder pointer in dlss5 evals
fix(gaming): drop dead ErrorPath branch; correct 0.8.1 and 0.8.2 chan…
kyle-sexton commentedon Sep 29, 2026
Reopening. This item was closed by PR #4911 (
Closes #4592) by mistake.reference/feeder-route.mdplus assess wording). It carried no maintainer decision. The "research park" it describes is a third option the maintainer did not offer.Verify-DLSS5Feeder.ps1in status) and items 6-9 (per-game consumer choice, Luma-on-64-bit refusal, depth-on-wrong-buffer surfacing, per-consumer presets and renodx-dlss5 settings ranges).Decision needed. Adopt the DLSS5-Feeder route into
gaming:dlss5, or scope this item down to the assess fixes already shipped?/work-items:decomposeinto a slice for detection, apply/remove/status with manifest, verifier in status, consumer checks, and per-consumer presets. The anti-cheat gate applies unchanged.SKILL.md,candidate-selection.mdandfeeder-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.feeder-route.mdas 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
#4592pointers 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 #4592and leaves this item open. No option is implemented.fix(gaming): gate the Feeder pointer on anti-cheat status and make it…
kyle-sexton commentedon Sep 29, 2026
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.
kyle-sexton commentedon Sep 29, 2026
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.
feat(gaming): run a report-only dlss5 update check before every action (