跳至主要內容
v2.2.9 · 無法存取

DLSS 5 Swapper 的 GitHub 頁面目前無法存取(檢查於 2026/11/11 16:15 UTC)。目前尚未公布任何原因。請勿從其他 GitHub 帳號或有密碼保護的壓縮檔下載。 工具狀態與安全的下一步

How to Get More FPS With DLSS 5 Swapper: 7 Settings

DLSS 5 neural rendering costs several milliseconds per frame. These seven settings recover the most FPS in DLSS 5 Swapper, from working resolution to frame gen.

2026/9/26 v2.2.9 DLSS5 Swapper Guide 最後更新: 2026/10/5 顯示英文版 3 分鐘閱讀

常見問題

Why does DLSS 5 Swapper lower my FPS?
DLSS 5 runs an AI model on every frame to relight it. That adds work, typically several milliseconds per frame at 4K. It improves the image, not the frame rate.
What is the best DLSS 5 Swapper setting for an RTX 3080 Ti?
There is no universal best preset. Start with Pass Count 1, the game's DLSS Balanced or Performance mode, and a working resolution below native, then raise quality until the frame rate is no longer acceptable.
Does DLSS 5 Swapper make my GPU run hotter?
It can: the tensor cores work every frame, so power draw and temperature usually rise. A frame-rate cap lowers both.
Does Multipass give more FPS?
No. Multipass runs the neural pass several times per frame for a stronger effect, so each extra pass costs more frame time.

Why DLSS 5 costs frame rate

DLSS 5 runs an AI model on every frame. DLSS5oneclick’s documentation puts it plainly: neural rendering at native 4K “adds several milliseconds”, and with V-Sync on at 60 Hz that shows up as a hard drop to 30 FPS. Even an RTX 5070 Ti at 4K went from 71 to 35 FPS in an early Control test (Tom’s Hardware). RTX 20 and 30 cards pay more. You cannot make it free, but these settings recover the most.

1. Keep Pass Count at 1

The Multipass route can run the neural pass up to ten times per frame. Each pass adds its full cost again. If you installed Multipass, set Pass Count to 1 in the Home panel, or switch back to the normal route.

2. Lower the working resolution (games without DLSS)

On the ReShade / Feeder route, the model runs at the Feeder’s working resolution, set by work_resolution in dlss5-feed.cfg next to the game’s executable (DLSS5-Feeder configuration). Lowering it is the single biggest saving; work_upscale then scales the result back to your screen. Try one step down, restart the game, and compare.

3. Use a stronger DLSS upscaling mode (games with DLSS)

In games with native DLSS, the game renders at a lower internal resolution before DLSS 5 relights the frame. Switching the game’s DLSS from Quality to Balanced or Performance reduces both the game’s cost and, depending on the route, the neural pass’s.

4. Turn off V-Sync, or cap the frame rate yourself

With V-Sync on, a frame that misses the refresh deadline waits for the next one, turning 55 FPS into 30. Turn V-Sync off in game (use G-SYNC/FreeSync if you have it) or set a frame cap slightly below your average instead.

5. Add frame generation — carefully

DLSS 5 adds image quality, frame generation adds smoothness; they combine well. On RTX 40 and 50, enable the game’s own DLSS Frame Generation. Community unlocks for older cards exist in other tools (RHI’s RTX 40 MFG unlock, DLSS5oneclick’s experimental RTX 20/30 option, DLSS 5 Manager’s Live Flow frame generation); see multi frame generation. Generated frames raise the counter, not responsiveness, so keep the base frame rate above about 50–60 FPS.

6. Close overlays and monitoring tools

The Swapper v2.2.7 notes single out MSI Afterburner and RivaTuner: people had fewer problems “especially with MSI Afterburner and RivaTuner closed”. Overlays hook the same rendering calls; close them while testing, then add them back one at a time.

7. Consider a tool with a cost scaler

RHI includes an NR Cost Scaler that runs the neural pass at reduced cost (75% by default). It is a different tool, so restore your Swapper install before switching. Compare tools in the tool comparison.

How to check a setting actually helped

  1. Pick one repeatable scene or benchmark and one resolution.
  2. Record average FPS and 1% lows for 60 seconds with the effect off, then on (F6 or the overlay toggle).
  3. Change one setting, restart if needed, and record again.
  4. Keep the change only if the numbers and the image both hold up.

Use the same method to judge heat: record GPU temperature and power alongside FPS. If the game becomes unstable, restore the originals and start again from the baseline. Check what your card can expect on the GPU compatibility page.

相關文章