sky_line/Slipstream

Fork 1

FSR 1/4: render resolution separate from display resolution #181

New issue

Closed

opened 2026-09-29 21:31:11 +00:00 by sky_line · 1 comment

sky_line commented

2026-09-29 21:31:11 +00:00

Owner

Part of #6 (FSR), epic #84. Needed by every upscaler (ours, FSR 3.1, a plain resolution divisor from #39).

Today one width, height runs through the whole VK frame. Split it:

Render size (scaled): depth pre-pass, motion vectors, HDR scene + depth, AO, SSR and its previous-frame copy, water / refraction copies, reactive reference, particles, occlusion Hi-Z, the main-view cluster grid.
Display size: the upscaler output and everything after it (DoF, bloom / glow / flare, exposure, eyedropper, tonemap, grading, SMAA/FXAA, final), selection outline, HUD, UI, snapshots.

Also:

Jitter is a fraction of a render pixel; TAA mip bias becomes log2(render / display) - 0.5 style.
Window resize or scale change resets history.
Mirror / probe captures and custom-size snapshots unaffected (or explicitly native).
Setting RenderVKRenderScale (1.0 = today, exact same path). Until the upscaler lands, the TAA resolve does the upscale with a simple filter so the path is testable end to end.

Done when: scale 1.0 is pixel-identical to today, and 0.5-0.77 renders and composites correctly with UI, HUD, selection, snapshots, mirrors and DoF all at display size.

Part of #6 (FSR), epic #84. Needed by every upscaler (ours, FSR 3.1, a plain resolution divisor from #39). Today one `width, height` runs through the whole VK frame. Split it: **Render size** (scaled): depth pre-pass, motion vectors, HDR scene + depth, AO, SSR and its previous-frame copy, water / refraction copies, reactive reference, particles, occlusion Hi-Z, the main-view cluster grid. **Display size**: the upscaler output and everything after it (DoF, bloom / glow / flare, exposure, eyedropper, tonemap, grading, SMAA/FXAA, final), selection outline, HUD, UI, snapshots. Also: - Jitter is a fraction of a *render* pixel; TAA mip bias becomes `log2(render / display) - 0.5` style. - Window resize or scale change resets history. - Mirror / probe captures and custom-size snapshots unaffected (or explicitly native). - Setting `RenderVKRenderScale` (1.0 = today, exact same path). Until the upscaler lands, the TAA resolve does the upscale with a simple filter so the path is testable end to end. Done when: scale 1.0 is pixel-identical to today, and 0.5-0.77 renders and composites correctly with UI, HUD, selection, snapshots, mirrors and DoF all at display size.

sky_line added the

rendering

perf

feature

labels

2026-09-29 21:31:11 +00:00

sky_line referenced this issue

2026-09-29 21:31:18 +00:00

FSR upscaling #6

sky_line referenced this issue from a commit

2026-09-29 22:05:48 +00:00

VK render scale: scene at a render resolution, upscaled by the TAA resolve

sky_line referenced this issue from a commit

2026-09-29 22:05:48 +00:00

TAA resolve: exact render-pixel position at native scale

sky_line referenced this issue from a commit

2026-09-29 22:05:48 +00:00

VK: re-write cached descriptor sets on target re-creation, not view change

sky_line referenced this issue from a commit

2026-09-29 22:05:48 +00:00

TAA upscale: coverage-weighted blend and a scale-sized jitter cycle

sky_line referenced this issue

2026-09-29 22:17:53 +00:00

Investigate: built-in ReShade-style user shader effects (load .fx effects in our post chain) #186

sky_line referenced this issue from a commit

2026-09-29 22:59:30 +00:00

Render scale: unjittered display depth for the display-space passes

sky_line referenced this issue

2026-09-29 22:59:51 +00:00

Z-fighting on near-coplanar surfaces (windowsills, frames); worse under TAA jitter -- reversed-Z #188

sky_line referenced this issue

2026-09-29 23:32:09 +00:00

Later: investigate integrating AMD FSR 3.1 upscaler as an alternative to our TAA upscaler #191

sky_line referenced this issue from a commit

2026-09-29 23:45:00 +00:00

Upscaling quality modes in Preferences and Quick Prefs

sky_line referenced this issue from a commit

2026-09-29 23:45:00 +00:00

Upscaling: Off means native (Custom mode for the free scale); AO radius in render pixels

sky_line commented

2026-09-29 23:45:10 +00:00

Author

Owner

Done and tested in-world (pushed up to 33a645cd0d): RenderVKRenderScale / RenderVKUpscaleMode, render-size scene targets with native-scale aliasing, unjittered display depth for overlays/selection/HUD, descriptor re-writes on target re-creation (mTargetGen), AO radius in render pixels. Measured on the 5090: native ~105-110 FPS -> Performance ~135 FPS.

Done and tested in-world (pushed up to 33a645cd0d): RenderVKRenderScale / RenderVKUpscaleMode, render-size scene targets with native-scale aliasing, unjittered display depth for overlays/selection/HUD, descriptor re-writes on target re-creation (mTargetGen), AO radius in render pixels. Measured on the 5090: native ~105-110 FPS -> Performance ~135 FPS.

sky_line referenced this issue

2026-09-29 23:45:10 +00:00

FSR upscaling #6

sky_line closed this issue

2026-09-29 23:45:10 +00:00

sky_line referenced this issue from a commit

2026-10-03 01:50:56 +00:00

VK snapshot crash / bloom wash-out: generation-keyed descriptor rewrites + post-offscreen reset

sky_line referenced this issue

2026-10-04 02:45:46 +00:00

FSR upscaling #6

sky_line referenced this issue