fix(vk): FSR 3.1 frame generation lays the HUD over each made frame's own scene: no halo of the real frame's background #1755

Merged
HumanBean merged 3 commits from madebyjordan/Longshot:fix/fg-smear into main 2026-11-19 17:51:44 +00:00
Member

Type: fix · Risk: medium · Tested on: Windows 11, RX 6700 XT (Adrenalin 26.10.1) · Needs: RX 9070 XT with FSR 4 Native AA and HDR (the #1565 reporters' setup); NVIDIA and Intel with FSR 3.1 FG; Linux

TL;DR

With AMD FSR 3.1 frame generation, every HUD element still carried a halo in the made frames on v3.0.0: the hearts' soft glow, the item box's shadow, the faint D-pad and Navi icons and the minimap showed the real frame's background through them, while the scene around had moved on. This PR learns how see-through each HUD pixel is from frame to frame and lays the HUD over each made frame's own scene instead. In the game on an RX 6700 XT the halo is gone (pictures below), with no frame-rate cost measured; a new game-free test fails on main and passes here.

Breakdown

  • Who it helps: everyone whose frames FSR 3.1 makes: AMD and Intel cards, NVIDIA before RTX 40, and Frame generation Auto on RTX 40 and up.
  • What was wrong: FSR 3.1 laid the presented pixel over the made frame wherever the HUD is, and where the HUD is see-through that pixel holds the real frame's scene, not the made frame's.
  • What changes: the HUD goes over each made frame as the game blends it, B + T × scene, with B (the HUD's colour) and T (how see-through it is) learned from the pictures before and after the HUD over successive frames; where T isn't known yet, the presented pixel as before.
  • What does not change: menus and movies, the HUD-less interpolation itself (#1487, #1538, #1691), DLSS FG and the built-in interpolator, settings, saves and caches.
  • How it was checked: the same renderer with RX_VK_FSR_FG_HUD_LAYER=0 (main's path) against unset, camera turns in the field, made frames shot and compared; 600 of 600 presents with the HUD layer; three interleaved frame-rate pairs; two game-free tests (one failing on main); a cold review by a second agent, its findings fixed.
  • What is still open: HDR (this monitor has no HDR10 swapchain), the reporters' RX 9070 XT, NVIDIA/Intel, Linux; limb ghosting in made frames (#1236) is a different problem and not touched.
  • Risk: medium: every FSR 3.1 made frame in play takes the new path; the fallback is the old path per pixel, and RX_VK_FSR_FG_HUD_LAYER=0 turns it off.

Why

#1565 (RX 9070 XT, FSR 4 Native AA, FSR 3.1 FG) still sees "ghosting around UI elements, more noticeable with HDR on" on 3.0.0 RC8, after #1487, #1538 and #1691. On this PC the HUD is marked on 600 of 600 presents with every upscaler at 100% (game's own, FSR 3.1, FSR 4, Off), so it is not a missing capture any more. Shooting the made frames shows what is left: since #1487 FSR 3.1 interpolates the picture from before the HUD and then lays the presented frame over the made frame wherever the two differ (FI_PATCHES 4: the pixel whole). Where the HUD is see-through, the presented pixel is the HUD blended over this frame's scene, so each HUD element drags a patch of the real frame's background into the made frame: a box of different sky around the hearts, the Navi icon and the D-pad, a dark band at the item box's edge, the minimap's see-through parts. Brighter backgrounds (HDR) make the mismatch larger.

The HUD itself can't be drawn again on its own here, but it stays where it is while the scene behind it moves. The game blends it as D = B + T × S (S the picture before the HUD, D after), so from one frame to the next D1 − D0 = T × (S1 − S0): T can be fitted per pixel from the two pictures the renderer already copies (#1464), and B follows.

Fixes #1565. See #1310, #1464, #1487, #1538, #1691; #1236 (limbs, separate).

How to reproduce

Seen on: Windows 11, RX 6700 XT, Adrenalin 26.10.1 (reported on RX 9070 XT, 26.10.1/26.11.1)
Settings and switches: Frame generation 2x, Frame generation by FSR 3.1 FG, any Upscaler (seen with the game's own and FSR 4 at 100%), 60 fps cap
Steps: Hyrule Field by the drawbridge (the bench save), turn the camera with the right stick; to see the made frames: RX_VK_SHOTS=<dir> RX_VK_SHOT_MADE=all RX_VK_SHOT_GO=<file> and create the file while turning
Expected: the HUD's glows, shadows and see-through icons show the same background as the made frame around them
Actual: a halo of the real frame's background around each HUD element in every made frame

What changed

A per-pixel fit of how see-through the HUD is, kept from frame to frame, and the HUD laid over each made frame by it. FSR 3.1 itself is given its HUD-less colour as its present too, so it lays nothing over its made frames.

  • shaders: gpu/vk/shaders/fg_hud_layer.comp (hud_fit: a least-squares fit of T over the colour's channels, decayed so newer frames count more; started again when T no longer explains a frame, i.e. the HUD changed; unknown where the HUD just appeared, nothing moved behind it yet, or the scene is brighter than the frame's 1; a fit that isn't a number starts again) and fg_hud_composite.comp (hud_over: B + T × the made frame's scene in the picture's encoding, the presented pixel where T is unknown); SPIR-V headers made with glslang 16.2.0, their first line naming the shader's hash.
  • framegen: gpu/vk/vk_framegen.cpp keeps two pairs of the before/after picture copies (this frame's and the frame before's), hud_layer() runs the fit after the mask pass, and fsr3fi_frames() gives FSR 3.1 the HUD-less colour as Inputs::present and lays the HUD over each made frame after copying it into the set. The 600-present fsr3fi line counts the presents with the HUD layer.
  • switch: RX_VK_FSR_FG_HUD_LAYER=0 lays the presented frame as before (gpu/vk/switches.def, docs/development.md); docs/temporal-history.md's FSR 3.1 HUD paragraph.
  • tests: tests/test_fsr3fi_hud_layer.py (new) runs hud_fit and hud_over, compiled as C++, over a HUD pixel through frames at B10G11R11's precision; tests/test_fsr3fi_hud_mask.py now checks the wiring (FSR 3.1's present, the fit's inputs from both frames, the lay-over after the copy, the fallback when the layer's pipelines fail).

Measurements

Verdict: fixed on this PC: the halo around the HUD is gone from the made frames while turning, 600 of 600 presents get the HUD layer, and the frame rate is the same within run-to-run noise.

Hardware: Windows 11 (26200), RX 6700 XT 12 GB, Adrenalin 26.10.1, Ryzen 5 5600, 16 GB
Scene: Hyrule Field by the drawbridge (bench/pinned-field slot 02), 1920x1080 window, the game's own upscaler at 100%, Frame generation 2x by FSR 3.1 FG
Method: the control bridge turning the camera (right stick, 4 s) with every present shot (RX_VK_SHOT_MADE=all); the made frames compared; the fsr3fi 600-present line; frame rate: the bridge's game fps each second for 40 s standing still, uncapped, three interleaved pairs, the median of each run.
Baseline: the same renderer with RX_VK_FSR_FG_HUD_LAYER=0, which is main's path (FSR 3.1 given the presented frame; no fit, no lay-over), so both columns share every other commit. The renderer was built from this branch and run on the v3.0.0 game folder (renderer interface 34 on both; vk_framegen.cpp, vk_fsr3fi.cpp and the HUD shaders are the same on v3.0.0 and main @ 8b0ea786). The first pictures (before any change) are v3.0.0's own shipped renderer. The commit after 642789ec adds only the run file (docs/tested).
How to reproduce: the steps above; RX_VK_FSR_FG_HUD_LAYER=0 for the before side.

Before, RX_VK_FSR_FG_HUD_LAYER=0 (main's path): this PR @ 642789ec After: this PR @ 642789ec
Made frames while turning halo of the real frame's background around the hearts, D-pad, Navi icon, item box the made frame's own background through the HUD's see-through parts
Presents with the HUD layer (of 600) 0 600
Game fps, uncapped, FG 2x (3 interleaved runs) 50.9 (50.9, 51.0, 50.9) 51.1 (50.9, 51.1, 51.1)
test_fsr3fi_hud_mask.py FAIL: in.present == in.color (main @ 8b0ea786) ok
test_fsr3fi_hud_layer.py fails: the shaders are missing (main @ 8b0ea786) ok
Before: vk: fsr3fi: of the last 600 presents 597 made by FSR 3.1, ...; 600 with the HUD marked, 0 with its HUD layer
After:  vk: fsr3fi: of the last 600 presents 597 made by FSR 3.1, ...; 600 with the HUD marked, 600 with its HUD layer
After:  vk: fsr3fi: the HUD laid over the made frames by how see-through it is, learned from frame to frame (1920x1080)

Made frames while turning, the same spot (Hyrule Field by the drawbridge, 1920x1080, the game's own upscaler, FSR 3.1 FG 2x), 2x crops. Top: Before, v3.0.0's own renderer (main's path; vk_framegen.cpp is the same on main @ 8b0ea786). Bottom: After, this PR @ 642789ec. Before: a light box of the real frame's sky around the hearts, a ragged dark edge left of the item box. After: the made frame's own sky and wall through them.

Hearts and item box in a made frame. Top: Before, v3.0.0's renderer (main's path). Bottom: After, this PR @ 642789ec

The minimap in the same two made frames. Left: Before (stone of the real frame along its lower edge). Right: After, this PR @ 642789ec.

Minimap in a made frame. Left: Before, v3.0.0's renderer. Right: After, this PR @ 642789ec

Not affected: build time and size (two small shaders), loading and caches (no pipeline cache change; two compute pipelines made at the first frame with FSR 3.1 FG). VRAM: +24 bytes a pixel of the output while FSR 3.1 FG runs in play (the fit and the layer, RGBA16F, and a second pair of picture copies): about 50 MB at 1080p, 88 MB at 1440p, 200 MB at 4K.

Flags and settings

One new switch, for an A/B.

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
RX_VK_FSR_FG_HUD_LAYER the HUD laid over FSR 3.1's made frames by how see-through it is (none: the presented pixel) on (unset); =0 the presented pixel as before no halo of the real frame's background around the HUD in made frames helps on RX 6700 XT Windows; untested on NVIDIA, Intel, Linux, HDR on for everyone

Testing

Tested: on this PC (Windows 11, RX 6700 XT, 26.10.1): FSR 3.1 FG 2x with the game's own upscaler and with FSR 4 at 100%, turning the camera in Hyrule Field; the made frames shot with the switch off and on: the halo is gone with it on (the drawbridge chain and the clouds continue behind the hearts' glow, the mountain ridge behind the D-pad and the Navi icon); 600/600 presents with the HUD layer in every window; no errors in the log. The game-free tests: test_fsr3fi_hud_layer.py and test_fsr3fi_hud_mask.py pass here, the mask test fails on main @ 8b0ea786 at in.present == in.color (FSR 3.1 given the presented frame), and both fail when the fix's key lines are broken (lay-over always presented; no restart when the HUD changes; no NaN reset; no brightness guard). The 20 checks that read vk_framegen.cpp, the switch table, the docs or the shaders pass; the full suite on Windows: 730 passed, 61 failed, 62 skipped, and the same 61 fail on main @ 8b0ea786 (Windows-only failures, none of them about this change). A second agent reviewed the diff cold; its findings (an uninitialised fit image, a loose tolerance, a scene over 1 behind the HUD, test gaps, memory) are fixed or listed here.

Not tested: HDR (Expanded and Native): this monitor offers no HDR10 swapchain; the pq path lays the HUD over in the picture's own encoding, as #1538 takes it. NVIDIA, Intel, Linux. Other areas than the field and the castle gate. 4x and Auto (the lay-over runs once per made frame).

Must be tested:

  • Windows, RX 9070 XT, FSR 4 Native AA, FSR 3.1 FG 2x, HDR on (the #1565 reporters): turn the camera in Hyrule Field, expecting no halo around the hearts, minimap and button prompts, and the log's fsr3fi line saying 600 with its HUD layer (by hand: a #1565 reporter)
  • Any GPU where FSR 3.1 makes the frames (linux, nvidia, intel): the same turn with Frame generation 2x by FSR 3.1 FG, expecting no crash and 600 with its HUD layer (Test Farm: @Beanstalk Frame generation 2x by FSR 3.1 FG, turning the camera in Hyrule Field, on Linux and NVIDIA)

Risks

What could break: the HUD's colour in made frames if the fit is wrong somewhere: a T that explains this frame within the picture's precision is used, else the presented pixel; an animated HUD (a beating heart, a count) shows the presented pixel for the frames it changes. A frame's last pass doing more than the plain encode over the picture would make the made frames' HUD differ from the real ones (#1538 already relies on the frame being the picture encoded). VRAM as above.

Turning it off: RX_VK_FSR_FG_HUD_LAYER=0.

Compatibility: nothing changes for a player after updating: no settings, saves, shader or pipeline caches, or renderer interface change.

Issues

Fixes #1565

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported.
  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen.
  • The SPIR-V headers regenerated with glslang (a shader changed).
  • A game-free test added for the fix, failing on main and passing here.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. (Windows built: the renderer alone with llvm-mingw, from 642789ec and from v3.0.0 with the same change. Linux not built here yet: the change is portable C++ and GLSL, no platform calls; the Test Farm run below builds it on Linux.)
  • Docs updated.

🤖 Generated with Claude Code

**Type:** fix · **Risk:** medium · **Tested on:** Windows 11, RX 6700 XT (Adrenalin 26.10.1) · **Needs:** RX 9070 XT with FSR 4 Native AA and HDR (the #1565 reporters' setup); NVIDIA and Intel with FSR 3.1 FG; Linux ## TL;DR With AMD FSR 3.1 frame generation, every HUD element still carried a halo in the made frames on v3.0.0: the hearts' soft glow, the item box's shadow, the faint D-pad and Navi icons and the minimap showed the real frame's background through them, while the scene around had moved on. This PR learns how see-through each HUD pixel is from frame to frame and lays the HUD over each made frame's own scene instead. In the game on an RX 6700 XT the halo is gone (pictures below), with no frame-rate cost measured; a new game-free test fails on main and passes here. ## Breakdown - **Who it helps:** everyone whose frames FSR 3.1 makes: AMD and Intel cards, NVIDIA before RTX 40, and Frame generation Auto on RTX 40 and up. - **What was wrong:** FSR 3.1 laid the presented pixel over the made frame wherever the HUD is, and where the HUD is see-through that pixel holds the real frame's scene, not the made frame's. - **What changes:** the HUD goes over each made frame as the game blends it, `B + T × scene`, with B (the HUD's colour) and T (how see-through it is) learned from the pictures before and after the HUD over successive frames; where T isn't known yet, the presented pixel as before. - **What does not change:** menus and movies, the HUD-less interpolation itself (#1487, #1538, #1691), DLSS FG and the built-in interpolator, settings, saves and caches. - **How it was checked:** the same renderer with `RX_VK_FSR_FG_HUD_LAYER=0` (main's path) against unset, camera turns in the field, made frames shot and compared; 600 of 600 presents with the HUD layer; three interleaved frame-rate pairs; two game-free tests (one failing on main); a cold review by a second agent, its findings fixed. - **What is still open:** HDR (this monitor has no HDR10 swapchain), the reporters' RX 9070 XT, NVIDIA/Intel, Linux; limb ghosting in made frames (#1236) is a different problem and not touched. - **Risk:** medium: every FSR 3.1 made frame in play takes the new path; the fallback is the old path per pixel, and `RX_VK_FSR_FG_HUD_LAYER=0` turns it off. ## Why #1565 (RX 9070 XT, FSR 4 Native AA, FSR 3.1 FG) still sees "ghosting around UI elements, more noticeable with HDR on" on 3.0.0 RC8, after #1487, #1538 and #1691. On this PC the HUD is marked on 600 of 600 presents with every upscaler at 100% (game's own, FSR 3.1, FSR 4, Off), so it is not a missing capture any more. Shooting the made frames shows what is left: since #1487 FSR 3.1 interpolates the picture from before the HUD and then lays the presented frame over the made frame wherever the two differ (`FI_PATCHES` 4: the pixel whole). Where the HUD is see-through, the presented pixel is the HUD blended over **this** frame's scene, so each HUD element drags a patch of the real frame's background into the made frame: a box of different sky around the hearts, the Navi icon and the D-pad, a dark band at the item box's edge, the minimap's see-through parts. Brighter backgrounds (HDR) make the mismatch larger. The HUD itself can't be drawn again on its own here, but it stays where it is while the scene behind it moves. The game blends it as `D = B + T × S` (S the picture before the HUD, D after), so from one frame to the next `D1 − D0 = T × (S1 − S0)`: T can be fitted per pixel from the two pictures the renderer already copies (#1464), and B follows. Fixes #1565. See #1310, #1464, #1487, #1538, #1691; #1236 (limbs, separate). ## How to reproduce **Seen on:** Windows 11, RX 6700 XT, Adrenalin 26.10.1 (reported on RX 9070 XT, 26.10.1/26.11.1) **Settings and switches:** Frame generation 2x, Frame generation by FSR 3.1 FG, any Upscaler (seen with the game's own and FSR 4 at 100%), 60 fps cap **Steps:** Hyrule Field by the drawbridge (the bench save), turn the camera with the right stick; to see the made frames: `RX_VK_SHOTS=<dir> RX_VK_SHOT_MADE=all RX_VK_SHOT_GO=<file>` and create the file while turning **Expected:** the HUD's glows, shadows and see-through icons show the same background as the made frame around them **Actual:** a halo of the real frame's background around each HUD element in every made frame ## What changed A per-pixel fit of how see-through the HUD is, kept from frame to frame, and the HUD laid over each made frame by it. FSR 3.1 itself is given its HUD-less colour as its present too, so it lays nothing over its made frames. - shaders: `gpu/vk/shaders/fg_hud_layer.comp` (`hud_fit`: a least-squares fit of T over the colour's channels, decayed so newer frames count more; started again when T no longer explains a frame, i.e. the HUD changed; unknown where the HUD just appeared, nothing moved behind it yet, or the scene is brighter than the frame's 1; a fit that isn't a number starts again) and `fg_hud_composite.comp` (`hud_over`: `B + T × the made frame's scene` in the picture's encoding, the presented pixel where T is unknown); SPIR-V headers made with glslang 16.2.0, their first line naming the shader's hash. - framegen: `gpu/vk/vk_framegen.cpp` keeps two pairs of the before/after picture copies (this frame's and the frame before's), `hud_layer()` runs the fit after the mask pass, and `fsr3fi_frames()` gives FSR 3.1 the HUD-less colour as `Inputs::present` and lays the HUD over each made frame after copying it into the set. The 600-present `fsr3fi` line counts the presents with the HUD layer. - switch: `RX_VK_FSR_FG_HUD_LAYER=0` lays the presented frame as before (`gpu/vk/switches.def`, docs/development.md); docs/temporal-history.md's FSR 3.1 HUD paragraph. - tests: `tests/test_fsr3fi_hud_layer.py` (new) runs `hud_fit` and `hud_over`, compiled as C++, over a HUD pixel through frames at B10G11R11's precision; `tests/test_fsr3fi_hud_mask.py` now checks the wiring (FSR 3.1's present, the fit's inputs from both frames, the lay-over after the copy, the fallback when the layer's pipelines fail). ## Measurements **Verdict:** fixed on this PC: the halo around the HUD is gone from the made frames while turning, 600 of 600 presents get the HUD layer, and the frame rate is the same within run-to-run noise. Hardware: Windows 11 (26200), RX 6700 XT 12 GB, Adrenalin 26.10.1, Ryzen 5 5600, 16 GB Scene: Hyrule Field by the drawbridge (`bench/pinned-field` slot 02), 1920x1080 window, the game's own upscaler at 100%, Frame generation 2x by FSR 3.1 FG Method: the control bridge turning the camera (right stick, 4 s) with every present shot (`RX_VK_SHOT_MADE=all`); the made frames compared; the `fsr3fi` 600-present line; frame rate: the bridge's game fps each second for 40 s standing still, uncapped, three interleaved pairs, the median of each run. Baseline: the same renderer with `RX_VK_FSR_FG_HUD_LAYER=0`, which is main's path (FSR 3.1 given the presented frame; no fit, no lay-over), so both columns share every other commit. The renderer was built from this branch and run on the v3.0.0 game folder (renderer interface 34 on both; `vk_framegen.cpp`, `vk_fsr3fi.cpp` and the HUD shaders are the same on v3.0.0 and main @ 8b0ea786). The first pictures (before any change) are v3.0.0's own shipped renderer. The commit after 642789ec adds only the run file (docs/tested). How to reproduce: the steps above; `RX_VK_FSR_FG_HUD_LAYER=0` for the before side. | | Before, RX_VK_FSR_FG_HUD_LAYER=0 (main's path): this PR @ 642789ec | After: this PR @ 642789ec | |---|---|---| | Made frames while turning | halo of the real frame's background around the hearts, D-pad, Navi icon, item box | the made frame's own background through the HUD's see-through parts | | Presents with the HUD layer (of 600) | 0 | 600 | | Game fps, uncapped, FG 2x (3 interleaved runs) | 50.9 (50.9, 51.0, 50.9) | 51.1 (50.9, 51.1, 51.1) | | `test_fsr3fi_hud_mask.py` | FAIL: `in.present == in.color` (main @ 8b0ea786) | ok | | `test_fsr3fi_hud_layer.py` | fails: the shaders are missing (main @ 8b0ea786) | ok | ``` Before: vk: fsr3fi: of the last 600 presents 597 made by FSR 3.1, ...; 600 with the HUD marked, 0 with its HUD layer After: vk: fsr3fi: of the last 600 presents 597 made by FSR 3.1, ...; 600 with the HUD marked, 600 with its HUD layer After: vk: fsr3fi: the HUD laid over the made frames by how see-through it is, learned from frame to frame (1920x1080) ``` Made frames while turning, the same spot (Hyrule Field by the drawbridge, 1920x1080, the game's own upscaler, FSR 3.1 FG 2x), 2x crops. Top: Before, v3.0.0's own renderer (main's path; `vk_framegen.cpp` is the same on main @ 8b0ea786). Bottom: After, this PR @ 642789ec. Before: a light box of the real frame's sky around the hearts, a ragged dark edge left of the item box. After: the made frame's own sky and wall through them. ![Hearts and item box in a made frame. Top: Before, v3.0.0's renderer (main's path). Bottom: After, this PR @ 642789ec](https://git.magicbean.dev/attachments/996cfbf0-3a79-4b6d-ac3a-721fc20af9a8) The minimap in the same two made frames. Left: Before (stone of the real frame along its lower edge). Right: After, this PR @ 642789ec. ![Minimap in a made frame. Left: Before, v3.0.0's renderer. Right: After, this PR @ 642789ec](https://git.magicbean.dev/attachments/241c42f0-e395-4b91-8945-3783c9d9d0d7) Not affected: build time and size (two small shaders), loading and caches (no pipeline cache change; two compute pipelines made at the first frame with FSR 3.1 FG). VRAM: +24 bytes a pixel of the output while FSR 3.1 FG runs in play (the fit and the layer, RGBA16F, and a second pair of picture copies): about 50 MB at 1080p, 88 MB at 1440p, 200 MB at 4K. ### Flags and settings One new switch, for an A/B. | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | `RX_VK_FSR_FG_HUD_LAYER` | the HUD laid over FSR 3.1's made frames by how see-through it is | (none: the presented pixel) | on (unset); `=0` the presented pixel as before | no halo of the real frame's background around the HUD in made frames | helps on RX 6700 XT Windows; untested on NVIDIA, Intel, Linux, HDR | on for everyone | ## Testing **Tested:** on this PC (Windows 11, RX 6700 XT, 26.10.1): FSR 3.1 FG 2x with the game's own upscaler and with FSR 4 at 100%, turning the camera in Hyrule Field; the made frames shot with the switch off and on: the halo is gone with it on (the drawbridge chain and the clouds continue behind the hearts' glow, the mountain ridge behind the D-pad and the Navi icon); 600/600 presents with the HUD layer in every window; no errors in the log. The game-free tests: `test_fsr3fi_hud_layer.py` and `test_fsr3fi_hud_mask.py` pass here, the mask test fails on main @ 8b0ea786 at `in.present == in.color` (FSR 3.1 given the presented frame), and both fail when the fix's key lines are broken (lay-over always presented; no restart when the HUD changes; no NaN reset; no brightness guard). The 20 checks that read `vk_framegen.cpp`, the switch table, the docs or the shaders pass; the full suite on Windows: 730 passed, 61 failed, 62 skipped, and the same 61 fail on main @ 8b0ea786 (Windows-only failures, none of them about this change). A second agent reviewed the diff cold; its findings (an uninitialised fit image, a loose tolerance, a scene over 1 behind the HUD, test gaps, memory) are fixed or listed here. **Not tested:** HDR (Expanded and Native): this monitor offers no HDR10 swapchain; the pq path lays the HUD over in the picture's own encoding, as #1538 takes it. NVIDIA, Intel, Linux. Other areas than the field and the castle gate. 4x and Auto (the lay-over runs once per made frame). **Must be tested:** - Windows, RX 9070 XT, FSR 4 Native AA, FSR 3.1 FG 2x, HDR on (the #1565 reporters): turn the camera in Hyrule Field, expecting no halo around the hearts, minimap and button prompts, and the log's `fsr3fi` line saying `600 with its HUD layer` (by hand: a #1565 reporter) - Any GPU where FSR 3.1 makes the frames (linux, nvidia, intel): the same turn with Frame generation 2x by FSR 3.1 FG, expecting no crash and `600 with its HUD layer` (Test Farm: @Beanstalk Frame generation 2x by FSR 3.1 FG, turning the camera in Hyrule Field, on Linux and NVIDIA) ## Risks **What could break:** the HUD's colour in made frames if the fit is wrong somewhere: a T that explains this frame within the picture's precision is used, else the presented pixel; an animated HUD (a beating heart, a count) shows the presented pixel for the frames it changes. A frame's last pass doing more than the plain encode over the picture would make the made frames' HUD differ from the real ones (#1538 already relies on the frame being the picture encoded). VRAM as above. **Turning it off:** `RX_VK_FSR_FG_HUD_LAYER=0`. **Compatibility:** nothing changes for a player after updating: no settings, saves, shader or pipeline caches, or renderer interface change. ## Issues Fixes #1565 ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported. - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. - [x] The SPIR-V headers regenerated with glslang (a shader changed). - [x] A game-free test added for the fix, failing on `main` and passing here. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [ ] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. (Windows built: the renderer alone with llvm-mingw, from 642789ec and from v3.0.0 with the same change. Linux not built here yet: the change is portable C++ and GLSL, no platform calls; the Test Farm run below builds it on Linux.) - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
test_fsr3fi_hud_mask: FSR 3.1 is given the HUD-less colour as its present too (on main the frame
as presented, which it lays over each made frame whole, the real frame's scene showing through the
HUD's see-through parts), the HUD layer pass gets this frame's pictures and the frame before's, and
each made frame gets the HUD laid over it. test_fsr3fi_hud_layer: the layer's maths (fg_hud_layer.comp
hud_fit, fg_hud_composite.comp hud_over) compiled as C++ over a HUD pixel through frames, and the
two SPIR-V headers.

Assisted-by: Claude Opus 5.5 (Anthropic), through Claude Code
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The HUD's soft glows and shadows, faint icons and the minimap let the scene through. FSR 3.1's
HUD-less mode laid the presented pixel over each made frame whole wherever the HUD is, so every HUD
element carried a patch of the real frame's background over the made frame's moved scene.

How see-through each HUD pixel is (T) is now learned from frame to frame: the HUD stays where it is
while the scene behind it moves, so D1 - D0 = T (S1 - S0) between the picture before and after the
HUD (shaders/fg_hud_layer.comp, a least-squares fit kept per pixel, started again when it no longer
explains a frame). FSR 3.1 is given the HUD-less colour as its present too, so it lays nothing over,
and each made frame gets B + T times its own scene (shaders/fg_hud_composite.comp). Where T is not
known yet the presented pixel, as before. RX_VK_FSR_FG_HUD_LAYER=0 turns it off for an A/B.

Assisted-by: Claude Opus 5.5 (Anthropic), through Claude Code
Co-Authored-By: Claude Opus 5.5 <[email protected]>
docs(tested): the FSR 3.1 HUD layer on an RX 6700 XT, three interleaved pairs
Some checks reported errors
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 22s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 32s
CI / Workflow lint (actionlint) (pull_request) Successful in 34s
Third-party parts / As their notes say (pull_request) Successful in 39s
beanstalk/linux 2/1 fail
beanstalk/windows+intel 0/1 pass, 0 running, 0 queued
beanstalk/approval approved by madebyjordan (reviewed)
PR description / Description follows the template (pull_request_target) Failing after 18s
beanstalk/windows+nvidia 0/1 pass, 2 error
e0e5e53dab
Assisted-by: Claude Opus 5.5 (Anthropic), through Claude Code
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Member

Tested in game: Windows 11, RX 6700 XT, Adrenalin 26.10.1: Hyrule Field by the drawbridge, FSR 3.1 FG 2x with the game's own upscaler and FSR 4 at 100%, turning the camera; this branch's renderer (642789ec) on the v3.0.0 game folder. Made frames shot with RX_VK_FSR_FG_HUD_LAYER=0 and unset: the halo around the hearts, D-pad, Navi icon, item box and minimap is gone with it on; 600/600 presents 'with its HUD layer'; same game fps (median 50.9 off, 51.1 on, three interleaved pairs uncapped); no errors.

Tested in game: Windows 11, RX 6700 XT, Adrenalin 26.10.1: Hyrule Field by the drawbridge, FSR 3.1 FG 2x with the game's own upscaler and FSR 4 at 100%, turning the camera; this branch's renderer (642789ec) on the v3.0.0 game folder. Made frames shot with RX_VK_FSR_FG_HUD_LAYER=0 and unset: the halo around the hearts, D-pad, Navi icon, item box and minimap is gone with it on; 600/600 presents 'with its HUD layer'; same game fps (median 50.9 off, 51.1 on, three interleaved pairs uncapped); no errors.
Author
Member

The before/after pictures (made frames, the same spot) are in the description now. Still open before ready: a Linux build (portable C++ and GLSL; asking the Test Farm next).

The before/after pictures (made frames, the same spot) are in the description now. Still open before ready: a Linux build (portable C++ and GLSL; asking the Test Farm next).
Author
Member

@Beanstalk Frame generation 2x by FSR 3.1 FG (RX_VK_FSR_FG=1 on NVIDIA), the game's own upscaler at 100%, turning the camera in Hyrule Field for a few seconds: on Linux (any GPU) and on Windows NVIDIA and Intel. Check it builds and runs, no crash, and the log's fsr3fi 600-present line says '600 with its HUD layer'; frame times against main.

@Beanstalk Frame generation 2x by FSR 3.1 FG (RX_VK_FSR_FG=1 on NVIDIA), the game's own upscaler at 100%, turning the camera in Hyrule Field for a few seconds: on Linux (any GPU) and on Windows NVIDIA and Intel. Check it builds and runs, no crash, and the log's fsr3fi 600-present line says '600 with its HUD layer'; frame times against main.
Member

Beanstalk test farm

Commit e0e5e53 · tier reviewed · approved by madebyjordan · dashboard

What will be tested · AI plan (gpt-6.1-terra)

Build and run main and the PR on Linux, Windows NVIDIA, and Windows Intel; the Windows Intel target will wait for an online tester. Each run uses 2x FSR 3.1 frame generation and the game's own upscaler in Hyrule Field, turns the camera, captures the HUD, and measures frame times. The run takes about 12 minutes per tester, excluding builds, and fails on a crash, a missing 600-present HUD-layer log line, a substantial frame-time regression, or a large screenshot difference. The screenshots are a general visual regression check; they do not specifically verify the halo on generated frames. No tester online now matches windows+intel: that target waits for one.

  • Where: linux (1-2 reports), windows+nvidia (1-2 reports), windows+intel (1-2 reports).
  • field-hud: from the repository's save kokiri-start (settings dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1; switches RX_VK_FSR_FG=1), then teleport to Hyrule Field, move the stick, take the picture field-hud to compare with main, measure field for 30 s (after 10 s warm-up); 1 run on each side.
  • Measured: crashes, frame times, stutters and hitches, the game's log.
  • The PR fails if: it crashes; or a picture differs from main by more than 15%; or frame time (p99) is more than 15% above main; or forbidden log lines is above 0; or expected log lines missing is above 0.
  • Time: about 12 min of game runs per tester (2 game starts), plus the two builds.

Done (started 16:45 UTC, last report 17:27 UTC). Comment @Beanstalk to run it again.

Target Reports Crash Frame p99 (ms) vs main VRAM peak (MB) vs main Result
linux · 1: linux+amd+radv+dgpu AMD Radeon RX 7900 XTX (RADV NAVI31), 26.2.7; 2: linux+amd+radv+dgpu AMD Radeon RX 9070 XT (RADV GFX1201), 26.2.6 2/1 1 2 none — — fail ⚠ outlier
windows+nvidia · 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 4070 Ti, 621.14.0 2/1 1 2 none — — error
windows+intel 0/1 — — — queued

Measurements · linux

Verdict: fail on linux (2/1 report): field-hud log_expected_missing.max failed.

Hardware: 1: linux+amd+radv+dgpu AMD Radeon RX 7900 XTX (RADV NAVI31), 26.2.7 AMD Ryzen 7 5800X3D 8-Core Processor, 64 GB RAM; 2: linux+amd+radv+dgpu AMD Radeon RX 9070 XT (RADV GFX1201), 26.2.6 11th Gen Intel(R) Core(TM) i9-11900KB @ 3.30GHz, 32 GB RAM
Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports
How to reproduce: the farm's plan above (@Beanstalk on this PR runs it again)

Before: main @ 8b0ea78 After: this PR @ e0e5e53
field-hud · forbidden log lines 0.0 0.0
field-hud · expected log lines missing 1.0 1.0 (+0%)

Flags and settings

None: the plan varied no setting, switch or build option.

Markdown for the PR description
## Measurements

**Verdict:** fail on linux (2/1 report): `field-hud log_expected_missing.max` failed.

Hardware: 1: linux+amd+radv+dgpu `AMD Radeon RX 7900 XTX (RADV NAVI31), 26.2.7` `AMD Ryzen 7 5800X3D 8-Core Processor, 64 GB RAM`; 2: linux+amd+radv+dgpu `AMD Radeon RX 9070 XT (RADV GFX1201), 26.2.6` `11th Gen Intel(R) Core(TM) i9-11900KB @ 3.30GHz, 32 GB RAM`  
Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them  
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports  
How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again)

| | Before: main @ 8b0ea78 | After: this PR @ e0e5e53 |
|---|---|---|
| field-hud · forbidden log lines | 0.0 | 0.0 |
| field-hud · expected log lines missing | 1.0 | 1.0 (+0%) |

### Flags and settings

None: the plan varied no setting, switch or build option.

Measurements · windows+nvidia

Verdict: could not be judged on windows+nvidia (2/1 report).

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0 AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 4070 Ti, 621.14.0 AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM
Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports
How to reproduce: the farm's plan above (@Beanstalk on this PR runs it again)

Nothing was measured: no metric came back.

Flags and settings

None: the plan varied no setting, switch or build option.

Markdown for the PR description
## Measurements

**Verdict:** could not be judged on windows+nvidia (2/1 report).

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti, 621.14.0` `AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM`  
Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them  
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports  
How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again)

Nothing was measured: no metric came back.

### Flags and settings

None: the plan varied no setting, switch or build option.
<!-- beanstalk:sticky --> ### Beanstalk test farm Commit `e0e5e53` · tier **reviewed** · approved by madebyjordan · [dashboard](https://beanstalk.magicbean.dev/prs/1755) **What will be tested** · AI plan (`gpt-6.1-terra`) Build and run main and the PR on Linux, Windows NVIDIA, and Windows Intel; the Windows Intel target will wait for an online tester. Each run uses 2x FSR 3.1 frame generation and the game's own upscaler in Hyrule Field, turns the camera, captures the HUD, and measures frame times. The run takes about 12 minutes per tester, excluding builds, and fails on a crash, a missing 600-present HUD-layer log line, a substantial frame-time regression, or a large screenshot difference. The screenshots are a general visual regression check; they do not specifically verify the halo on generated frames. No tester online now matches windows+intel: that target waits for one. - **Where:** linux (1-2 reports), windows+nvidia (1-2 reports), windows+intel (1-2 reports). - **field-hud:** from the repository's save `kokiri-start` (settings dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1; switches `RX_VK_FSR_FG=1`), then teleport to Hyrule Field, move the stick, take the picture field-hud to compare with main, measure field for 30 s (after 10 s warm-up); 1 run on each side. - **Measured:** crashes, frame times, stutters and hitches, the game's log. - **The PR fails if:** it crashes; or a picture differs from main by more than 15%; or frame time (p99) is more than 15% above main; or forbidden log lines is above 0; or expected log lines missing is above 0. - **Time:** about 12 min of game runs per tester (2 game starts), plus the two builds. Done (started 16:45 UTC, last report 17:27 UTC). Comment `@Beanstalk` to run it again. | Target | Reports | Crash | Frame p99 (ms) vs main | VRAM peak (MB) vs main | Result | | --- | --- | --- | --- | --- | --- | | linux · 1: linux+amd+radv+dgpu `AMD Radeon RX 7900 XTX (RADV NAVI31), 26.2.7`; 2: linux+amd+radv+dgpu `AMD Radeon RX 9070 XT (RADV GFX1201), 26.2.6` | 2/1 [1](https://beanstalk.magicbean.dev/reports/rp_fbf060c36cfa9fe7) [2](https://beanstalk.magicbean.dev/reports/rp_ef5a17016f8f96cf) | none | — | — | fail ⚠ outlier | | windows+nvidia · 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti, 621.14.0` | 2/1 [1](https://beanstalk.magicbean.dev/reports/rp_550f9dc58d7bf2d5) [2](https://beanstalk.magicbean.dev/reports/rp_ca8db1bdceb61cc3) | none | — | — | error | | windows+intel | 0/1 | — | — | — | queued | #### Measurements · linux **Verdict:** fail on linux (2/1 report): `field-hud log_expected_missing.max` failed. Hardware: 1: linux+amd+radv+dgpu `AMD Radeon RX 7900 XTX (RADV NAVI31), 26.2.7` `AMD Ryzen 7 5800X3D 8-Core Processor, 64 GB RAM`; 2: linux+amd+radv+dgpu `AMD Radeon RX 9070 XT (RADV GFX1201), 26.2.6` `11th Gen Intel(R) Core(TM) i9-11900KB @ 3.30GHz, 32 GB RAM` Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 8b0ea78 | After: this PR @ e0e5e53 | |---|---|---| | field-hud · forbidden log lines | 0.0 | 0.0 | | field-hud · expected log lines missing | 1.0 | 1.0 (+0%) | ### Flags and settings None: the plan varied no setting, switch or build option. <details><summary>Markdown for the PR description</summary> ```markdown ## Measurements **Verdict:** fail on linux (2/1 report): `field-hud log_expected_missing.max` failed. Hardware: 1: linux+amd+radv+dgpu `AMD Radeon RX 7900 XTX (RADV NAVI31), 26.2.7` `AMD Ryzen 7 5800X3D 8-Core Processor, 64 GB RAM`; 2: linux+amd+radv+dgpu `AMD Radeon RX 9070 XT (RADV GFX1201), 26.2.6` `11th Gen Intel(R) Core(TM) i9-11900KB @ 3.30GHz, 32 GB RAM` Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 8b0ea78 | After: this PR @ e0e5e53 | |---|---|---| | field-hud · forbidden log lines | 0.0 | 0.0 | | field-hud · expected log lines missing | 1.0 | 1.0 (+0%) | ### Flags and settings None: the plan varied no setting, switch or build option. ``` </details> #### Measurements · windows+nvidia **Verdict:** could not be judged on windows+nvidia (2/1 report). Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti, 621.14.0` `AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM` Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) Nothing was measured: no metric came back. ### Flags and settings None: the plan varied no setting, switch or build option. <details><summary>Markdown for the PR description</summary> ```markdown ## Measurements **Verdict:** could not be judged on windows+nvidia (2/1 report). Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 3050 Ti Laptop GPU, 621.24.0` `AMD Ryzen 7 5800H with Radeon Graphics, 16 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti, 621.14.0` `AMD Ryzen 9 5900X 12-Core Processor, 64 GB RAM` Scene: field-hud, from the repository's save kokiri-start (dlss=0, resolution=0, frame_rate_cap=0, frame_generation=2, frame_generation_by=1, RX_VK_FSR_FG=1); each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); field-hud: 1 game start a side, field 30 s after 10 s warm-up; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) Nothing was measured: no metric came back. ### Flags and settings None: the plan varied no setting, switch or build option. ``` </details>
HumanBean changed title from WIP: fix(vk): FSR 3.1 frame generation lays the HUD over each made frame's own scene: no halo of the real frame's background to fix(vk): FSR 3.1 frame generation lays the HUD over each made frame's own scene: no halo of the real frame's background 2026-11-19 17:51:32 +00:00
HumanBean deleted branch fix/fg-smear 2026-11-19 17:51:45 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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
MagicBeanDev/Longshot!1755
No description provided.