DLSS5-Autopilot Explained: 8 Routes, 546 Stars, Zero Bundled Binaries [2026]
Friday, September 11, 2026Updated September 11, 2026: Kizzuwatnaa's DLSS5-Autopilot is the one-click front end for the entire DLSS 5 mod scene. It scans 12 game launchers plus 19 emulators, detects each game's graphics API from its executable, picks among 8 install routes, fetches every component from its original publisher, and verifies GPU compatibility down to CUDA architecture. It holds 546 stars and 28 forks across 148 commits, bundles nothing, and needs no admin rights. Here is how the route picker works, what each route does, and how the safety model holds together.
Table of Contents
- What DLSS5-Autopilot Is
- The Library Scan: 12 Launchers, 19 Emulators
- The 8 Routes, Explained
- Per-Card Builds: Full Speed to Half FPS
- Frame Generation Switches
- Video, YouTube, Webcam, Screen
- The Safety Model
- Routes at a Glance
- When It Does Not Work
- Bottom Line
- Frequently Asked Questions
1. What DLSS5-Autopilot Is
DLSS5-Autopilot by Kizzuwatnaa puts DLSS 5 neural rendering into games that never shipped it, automating a setup the community previously assembled by hand from a dozen repositories. One executable, nothing to install, no admin rights: run it, scan games, pick a title, press INSTALL, and start the game with the named key. Uninstall removes exactly what was written and restores anything replaced. The repository holds 546 stars, 28 forks, 6 watchers, 45 issues, and 148 commits.
The design principle is stated up front: the repository holds installer logic only, with no game files, NVIDIA binaries, or third-party code redistributed. Every component downloads at run time from its original publisher, resolved fresh on each run. Our earlier Autopilot coverage tracked its performance story and our mod roundup placed it in the wider scene. This article is the full manual.
Swapping a DLL alone does nothing on any card, as the README explains: outside NBA 2K27 no game asks for neural rendering, so the request itself must come from an add-on or OptiScaler. The tool exists to manufacture that request correctly per game, which is why route selection is its central mechanic rather than a settings page.
2. The Library Scan: 12 Launchers, 19 Emulators
Pressing scan games reads Steam, Epic, GOG, EA, Ubisoft, Battle.net, Rockstar, Amazon, itch, Heroic, Xbox and Game Pass, D:\Games style folders, and 19 emulators, with a manual folder picker for anything else. Scan-at-start is the default, rescan walks disks again after installs or removals, and findings persist in a local library.json so later launches open instantly. The scan never walks whole disks and skips removable drives, reading launcher registries and known folder patterns instead.
Each game card shows what was detected: executable, 32 or 64-bit, graphics API, and whether it ships DLSS, plus the route the tool will take. API detection reads the executable's import table, with special handling for liars: Unreal-era D3D9 imports get checked against delay-load tables and Agility SDKs, engines that load renderers at run time get ranked by DLL names, Unity titles default to D3D11 unless forced otherwise, and R.U.S.E., which links D3D11 but renders D3D9, gets a manual override dropdown remembered per folder.
Xbox and Game Pass titles appear only where publishers permit modding through the Xbox app's file browsing. Without that permission no tool can modify the folder, and the Steam version becomes the practical answer. Anti-cheat titles from BattlEye to Vanguard to Ricochet get flagged in the list with a confirmation gate before install, since ReShade add-ons and anti-cheat do not coexist and bans fall on the installer.
3. The 8 Routes, Explained
Native hooks the DLSS calls a 64-bit D3D12 game already makes, via Krish's renodx-dlss5 add-on, with OptiScaler recommended first on RTX cards. Neural-upstream runs matiasLombo's network at render resolution before the game's own DLSS upscales, with a cadence dial for every first, second, or third frame. Optiscaler replaces the upscaler through Dagherbou's fork, or alternates, running the model over output with model resolution from 25 to 100 percent plus optional FSR 3.1 frame generation on any card.
Bridge mirrors the game's DLSS contract onto a private D3D12 session via NIGos' dlss5-bridge, serving D3D11 and Vulkan games with DLSS. Feeder builds a synthetic DLAA contract from ReShade depth and motion vectors via jlrouzies-fr's project, covering games with no DLSS across D3D10, 11, 12, Vulkan, OpenGL, and 32-bit titles through a host64 helper and DX9 through DXVK. Standalone runs kibblerz's self-fed add-on with its own window for 64-bit D3D11 and 12 with or without DLSS, experimental.
Renodx-dlss hooks D3D9, 11, and 12 in-process through ShortFuse's add-on, the only route reaching 64-bit DirectX 9, though reported failing in many other games. Remix detects an RTX Remix mod's .trex folder and runs DLSS 5 inside the Remix runtime after its upscaler, injecting nothing. Two overrides beat the diagram: a Remix mod present always means remix since ReShade crashes Remix games, and anti-cheat always demands confirmation first.
4. Per-Card Builds: Full Speed to Half FPS
The neural runtime compiles per architecture, and the tool detects the card, picks the matching build, and verifies CUDA fatbin records before installing. RTX 50 runs NVIDIA's own 310.8.0 build at full speed. RTX 40 takes the community sm_89 re-target at moderate cost. RTX 20 and 30 take FP16 community builds at heavy cost, roughly half the frame rate at 100% model resolution, with the work-area dial as relief.
The work-area slider is the great equalizer: 75% costs about half of 100%, 50% a quarter, since cost falls with the square while the frame keeps full detail. An aim-for-FPS mode computes the work area from measured runs of that game, states its confidence, and never applies anything unasked. GTX and 16-series cards do not run at all. AMD and Intel cards get an explanation pointing at the two Radeon HIP projects, installable as a route the day either publishes everything openly.
Driver 616.64 and newer need attention. NVIDIA's DLSS 5 launch drivers route the neural feature into the runtime itself, and the 4.6 and 4.7 add-ons fault on every evaluate there while 4.55 passes 300 of 300. The tool installs 4.55 automatically on these drivers unless a build is hand-picked, and 616.56 remains the surest driver for full compatibility. The bridge route and standalone route offer alternative workarounds documented per game.
5. Frame Generation Switches
Two switches, both off by default. First, frame generation on any RTX card through the optiscaler route on D3D12: OptiScaler's bundled FSR 3.1 libraries generate one frame per rendered frame, 2x, on RTX 20 through 50, with the game's own generation switched off and added latency expected. Second, multi-frame generation on RTX 40 through ReShade routes on D3D12 and Vulkan: dashdogy's RTX40MFG-Unlock raises an existing DLSS frame generation multiplier to 3x or 4x in memory with Ada temporal correction, placed via Ultimate ASI Loader, offered only where the game already ships the generation DLLs.
The distinction is load-bearing. The first creates generation where none existed. The second only multiplies generation the game already has, and NVIDIA's own multi-frame generation stays an RTX 50 feature. Research software warnings apply to higher multipliers and Vulkan: freezes and crashes are possible, and the multiplier lives in ReShade's DLSS MFG tab.
HUD behavior varies by game and is the honest caveat. Generated frames can smear interface elements that the engine draws outside the 3D pipeline, and no tool fixes that universally. Test the game's HUD in motion before trusting multiplied numbers.
6. Video, YouTube, Webcam, Screen
The video and YouTube page fetches portable MPC-HC, sets D3D11 rendering, and installs DLSS 5 into the player like a game. Open files, paste YouTube links for live yt-dlp playback or download-first processing, render clips offline, or point a webcam at it. F6 toggles the effect during playback. Neural rendering redraws the whole window including menus, so text takes on a hand-drawn look.
The screen rows capture the desktop itself through GPU duplication with NVENC at 30 FPS, playing it back through DLSS 5 about half a second behind: browser video, emulators, calls, even anti-cheat games since nothing injects into the source. Single-monitor setups capture the left 62% with the player parked right; dual monitors capture fullscreen to the other display. Window mode captures one window anywhere for fullscreen overlay. The delay makes it a watching tool, not a playing tool.
This page is the project's quiet killer feature. Every game-specific caveat vanishes when the game is just pixels on a screen, anti-cheat included. Half a second of latency disqualifies interaction and changes nothing about spectating, and for stream watchers and archivists that tradeoff is pure win.
7. The Safety Model
Every release builds on GitHub Actions from the tagged commit, never uploaded by hand, with SHA-256 sums and signed provenance attestations verifiable through standard tooling. The program runs as plain Python from source with standard library and tkinter only, writes solely into chosen game folders plus one announced Vulkan registry value, keeps cache in local app data, requests no admin rights, and sends no telemetry. Network destinations are enumerated in source: ReShade, GitHub raw and API, and object hosts, nothing else.
Antivirus friction is documented rather than denied. Defender cloud heuristics flag new releases in their first hours by novelty scoring, the same files pass a day later, every release gets submitted to Microsoft as a false positive, and SmartScreen warnings reflect the missing paid certificate rather than file content. Code signing runs through SignPath on GitHub-hosted runners with owner-only approval, so a signed exe matches its tagged commit exactly.
Diagnostics close the loop. A did-it-work check reads ReShade, Feeder, OptiScaler, DXVK, and Remix logs plus Windows Application Error records, naming causes from hook-quit games to depth-buffer mismatches. Bug reports pre-fill version, card, driver, game, route, diagnosis, and log tails for browser review before anything is filed. Compatibility reports aggregate per game until five results let the next user see which route won most often. Nothing transmits without the user seeing it first.
8. Routes at a Glance
| Route | Fits | Dial |
|---|---|---|
| native | 64-bit D3D12 with DLSS | Game's DLSS mode |
| neural-upstream | 64-bit D3D12 with DLSS | Cadence every 1st, 2nd, 3rd frame |
| optiscaler | 64-bit D3D11/12, DLSS/FSR/XeSS redirected | Model resolution 25-100%, optional FG |
| bridge | D3D11 and Vulkan with DLSS | Game's DLSS mode |
| feeder | No-DLSS games, D3D10/11/12, Vulkan, GL, 32-bit | Work area 50-100% |
| standalone-dlssnr | 64-bit D3D11/12, DLSS optional, experimental | Sub-native rendering |
| renodx-dlss | 64-bit DirectX 9 | Game's DLSS mode |
| remix | Games with RTX Remix mods | Remix Neural Uplift sliders |
9. When It Does Not Work
| Symptom | Fix |
|---|---|
| Game quits on ReShade hook | DXVK path renders on Vulkan outside the hook, borderless mode |
| Driver 616.64+, nothing changes | Add-on 4.55 auto-installed, or bridge, standalone, or roll back to 616.56 |
| Logs succeed, picture unchanged | Borderless or true fullscreen at native resolution, then F6 |
| RE Engine instant crash | REFramework installed first, detected automatically |
| Antivirus quarantine | Restore, exclude game folder, run from source if needed |
10. Bottom Line
DLSS5-Autopilot is the scene's installer, librarian, diagnostician, and compatibility database in one executable that refuses to bundle anything it cannot license. Eight routes cover every API from DirectX 9 to Vulkan plus Remix and video, per-card builds match silicon honestly including the heavy FP16 truth for older cards, and the safety model of signed CI builds plus zero telemetry survives scrutiny. Five hundred forty-six stars undercounts its importance: this is the tool most users should start with, and the compatibility data it aggregates quietly becomes the scene's map of what works where.
Frequently Asked Questions
Q: What does DLSS5-Autopilot do?
A: It scans your game library across 12 launchers and 19 emulators, detects each game's API and DLSS status, picks among 8 install routes, downloads every component from original publishers, configures ReShade, and verifies results from game logs, all without admin rights.
Q: Which GPUs work?
A: RTX 50 at full speed with NVIDIA's build, RTX 40 moderate with community sm_89, RTX 20 and 30 heavy FP16 at roughly half FPS with work-area relief. GTX cards do not run. AMD cards get pointers to the two Radeon HIP projects.
Q: Is it safe and private?
A: Releases build on GitHub Actions with SHA-256 sums and signed attestations, the code runs as plain Python from source, nothing transmits without review, no telemetry exists, and antivirus flags are documented novelty heuristics with a Microsoft false-positive pipeline.
Q: What about anti-cheat games?
A: Flagged in the library with a confirmation gate. ReShade add-ons and anti-cheat do not coexist, and bans fall on whoever installs anyway. The screen-capture video path watches such games without injecting anything.
Q: What is new in recent versions?
A: Per the trajectory in our earlier coverage: pre-upscaler neural placement, DLSS5-Feeder integration for non-DLSS games, frame generation switches, the video and screen pages, Remix support with two one-click mod installs, and community compatibility aggregation at five reports per game.
Q: Does it really bundle nothing?
A: Correct. The repository holds installer logic only. Closed-source add-ons and runtimes download from community mirrors exactly as a manual install would, with the licensing implications stated in the README's credit table. Uncomfortable users should not use it.
Byline: Indie Kings | September 11, 2026
Labels: Hardware
Related: DLSS 5 Mods Explode: Dual GPUs, AMD Mode, 59 to 107 FPS | DLSS5 Autopilot: More Games, Lower Cost | NBA 2K27 DLSS 5 Verdict: 370 FPS Claim Tested