FSR 3.1 frame generation #1544

Closed
opened 2026-11-15 03:32:23 +00:00 by TheSlowly · 1 comment
Collaborator

Part of #1114 (Phase 2), follow-up of #1517 and #1536.

Frame generation for GPUs that can't run DLSS frame generation (AMD, Intel, NVIDIA RTX 20/30 and GTX): AMD's FSR 3.1 frame generation, MIT-licensed, vendored as source next to the FSR upscaler and driven by our own code. No AMD runtime or DLLs, so it works on Windows and Linux.

  • It sits behind the same generator call as DLSS frame generation. The swapchain, present thread, pacer, interface layer (HDR and SDR), composites and moving name tags stay as they are.
  • 2x only (FSR generates one frame per real frame). Paced by the viewer.
  • The viewer picks the generator automatically (DLSS where it can run, else FSR); a hidden setting can force one. The status line names the generator in use. Frame generation stays off by default.
  • Needs depth and motion vectors: DLSS or FSR upscaling on.

Open: today frame generation needs a second queue of the graphics family to present from, which AMD and Intel drivers may not offer. Supporting a single graphics queue is a separate step, after NVIDIA-testable parts land.

Part of #1114 (Phase 2), follow-up of #1517 and #1536. Frame generation for GPUs that can't run DLSS frame generation (AMD, Intel, NVIDIA RTX 20/30 and GTX): AMD's FSR 3.1 frame generation, MIT-licensed, vendored as source next to the FSR upscaler and driven by our own code. No AMD runtime or DLLs, so it works on Windows and Linux. - It sits behind the same generator call as DLSS frame generation. The swapchain, present thread, pacer, interface layer (HDR and SDR), composites and moving name tags stay as they are. - 2x only (FSR generates one frame per real frame). Paced by the viewer. - The viewer picks the generator automatically (DLSS where it can run, else FSR); a hidden setting can force one. The status line names the generator in use. Frame generation stays off by default. - Needs depth and motion vectors: DLSS or FSR upscaling on. Open: today frame generation needs a second queue of the graphics family to present from, which AMD and Intel drivers may not offer. Supporting a single graphics queue is a separate step, after NVIDIA-testable parts land.
TheSlowly added this to the Slipstream project 2026-11-15 03:32:23 +00:00
Author
Collaborator

Merged to main in 2834e00bf5 (PR #1555).

Merged to main in 2834e00bf5 (PR #1555).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#1544
No description provided.