DLSS5-Swapper
Install, tune and restore DLSS 5 in your games with one click. Native RenoDX, DLSS5-Feeder for games without DLSS, OptiScaler and multipass routes; DirectX 8/9/11/12, Vulkan, OpenGL, DirectDraw and emulators. In-game F8 overlay, automatic backups, and a community page showing what works on your games and your graphics card.
Runs with mockssource: GitHubJavaScriptMITcommit 24bd2aca7a74
JavaScript, MIT licensed.
DLSS5-Swapper runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed (404 packages), all 273 test subtests pass (0 failures, 2 intentionally skipped), all 26 core Node.js modules load correctly, and the Electron runtime is present at v33.4.11 but the GUI cannot launch without a GPU in this headless container.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- api-override-ipc.test.js: on Linux, main.js install handler calls steam() to find Proton prefix which fails without stubs5 minutes
- history-ipc.test.js: same root cause as above5 minutes
- backend-profile.test.js: file-journal safePath() does not detect Windows backslash path traversal on Linux5 minutes
- shader-compiler.test.js: retireOldShaderCompiler needs SystemRoot pointing to a System32 with D3DCompiler_47.dll4 minutes
- payload-guidance.test.js: path.join uses / on Linux, tests expect backslashes3 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm test exited 0: 273 subtests, 278 test functions, 0 failures, 2 skipped. 26/26 core modules load without Electron. Electron v33.4.11 is installed but the GUI could not launch (no GPU in container).
- Model tokens used
- 216,470
- Exact commit tested
- 24bd2aca7a74
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# cancelled 0 # skipped 2 # todo 0 # duration_ms 15724.63288 exec /bin/sh -lc 'echo "Started: approximately 30 min ago"' in /work/repo succeeded in 0ms: Started: approximately 30 min ago Now let me compile my final report. tokens used 216,470 Now let me compile my final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 25 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 JavaScript projects Argusic has installed and timed, DLSS5-Swapper was the 4th fastest to reach a running state, and 1 of 4 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.17 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dlss5-swapper)Questions
- Does DLSS5-Swapper run?
- DLSS5-Swapper runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test DLSS5-Swapper?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 24bd2aca7a74. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test DLSS5-Swapper?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does DLSS5-Swapper take to install?
- 25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does DLSS5-Swapper need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing DLSS5-Swapper?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does DLSS5-Swapper compare with the alternatives?
- Of the 4 JavaScript projects Argusic has installed and timed, DLSS5-Swapper was the 4th fastest to reach a running state, and 1 of 4 reached one at all.
- Where is the evidence for DLSS5-Swapper?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.