fix(vk): FSR 3.1 frame generation interpolates the picture from before the HUD and lays the frame's HUD over it #1487

Merged
HumanBean merged 1 commit from HumanBean/Longshot:fix/fsr-fg-hudless into main 2026-11-18 00:14:06 +00:00
Owner

Type: fix · Risk: medium · Tested on: Linux, RTX 3090 · Needs: AMD (Windows and Linux), Intel

TL;DR

With AMD FSR 3.1 frame generation, the HUD still breaks up in the made frames when the camera turns, on nightly-429 with #1464: hearts and icons speckle, and pieces of the minimap trail behind it. This PR gives FSR 3.1 the picture from just before the game draws its HUD, so it moves only the scene, then lays the real HUD over each made frame. That's how AMD's SDK is meant to handle a HUD. In the game the HUD stayed clean while turning, where #1464's way left red specks under the hearts.

Breakdown

  • Who it helps: anyone 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 interpolated frames with the HUD in them, so the frame before's HUD was dragged with the scene, and its colours spread into the gaps a turn opens.
  • What changes: in play, FSR 3.1 interpolates the HUD-less picture #1464 already copies, and AMD's own pass puts this frame's HUD on top.
  • What does not change: menus and movies (no such picture) keep today's path; settings, saves and the shader caches are untouched; the DLSS FG and built-in paths are untouched.
  • How it was checked: an A/B in the game on an RTX 3090, the same build with RX_VK_FSR_FG_HUDLESS=0 against it: 600 of 600 presents made by FSR 3.1 with the HUD-less picture, no errors, the HUD clean in the made frames. The person I work for played it and confirmed the HUD no longer breaks up.
  • What is still open: a run on AMD and on Intel; tests/run_all.py has not been run (see Testing).
  • Risk: medium: every FSR 3.1 made frame in play takes a new path; RX_VK_FSR_FG_HUDLESS=0 goes back to #1464's.

Why

#1464 marked the HUD in the alpha of the frame FSR 3.1 interpolates, and patched AMD's passes to keep those pixels still. The HUD still breaks up with nightly-429 (a 10 s clip of Hyrule Field turning, FSR 3.1 FG): in the made frames the hearts, the D-pad and Navi icons dissolve into speckles of the scene behind them, the minimap's arrow smears, and part of the minimap trails beside it.

Two things the mark can't fix: FSR 3.1 keeps the frame before, HUD and all, as its previous source, and a turn drags that HUD with the scene; and its inpainting fills the holes a turn opens from a pyramid built over the made frame, which already has the HUD written in, so the HUD's colours spread into them.

AMD's SDK has a mode for games like this one: give the frame without the HUD as the interpolation source, and the presented frame beside it. The interpolation then never sees a HUD, and the inpainting pass lays the presented frame over the made one wherever the two differ (HUDLessAttachedFactor). #1464 already copies exactly that picture (framegen_hud_before), so it only had to be handed over.

See #1310 (closed by #1464, still seen), #1420, #1464.

How to reproduce

Seen on: nightly-429; reported in a clip from a PC other than this one; on this PC (Linux, RTX 3090, NVIDIA 620.70.06) the red specks under the hearts below
Settings and switches: Frame generation 2x with Frame generation by FSR 3.1 FG (RX_VK_FSR_FG=1 on NVIDIA), the game's own upscaler
Steps: Kokiri Forest from the start save, next to Saria ("A Talk" shows), turn the camera with the right stick; or anywhere in Hyrule Field, turning fast
Expected: the HUD stays still and whole in the made frames
Actual: in the made frames, scene speckles in the hearts and icons, the minimap's arrow smeared, HUD pixels trailing below the hearts and beside the minimap

What changed

FSR 3.1 is now given AMD's HUD-less colour in play: the picture copied right after the gameplay upscale, cropped as the presented frame, and the presented frame beside it. History resets when a frame switches between the two kinds of source.

  • shader: gpu/vk/shaders/fg_hud.comp writes the copy, cropped as the frame, to a second image (hudless) next to the marked source; fg_hud_comp_spv.h regenerated.
  • framegen: gpu/vk/vk_framegen.cpp hud_source() makes and binds hud.hudless; fsr3fi_frames() gives it as in.color and the presented frame as in.present (the marked source with RX_VK_FSR_FG_HUDLESS=0, as before).
  • FSR 3.1 backend: gpu/vk/vk_fsr3fi.h Inputs::present; gpu/vk/vk_fsr3fi.cpp generate() sets hudless_attached_factor and binds present as the inpainting pass's present backbuffer (binding 2), leaves the HUD patches' flags off (no HUD in either source to keep), and resets when the previous source was the other kind.
  • switch: RX_VK_FSR_FG_HUDLESS (gpu/vk/switches.def, docs/development.md).
  • check: tests/test_fsr3fi_hud_mask.py follows the mask pass's fifth binding and the HUD-less inputs.

Measurements

Verdict: the HUD stays clean in FSR 3.1's made frames where #1464's mark left specks; no cost measured (one extra RGBA8 store per pixel in the existing mask pass), frame times not compared.

Hardware: Linux (CachyOS, kernel 7.3.3), RTX 3090, NVIDIA 620.70.06
Scene: Kokiri Forest from the start save next to Saria, 2560x1440 headless, the game's own upscaler, Frame generation 2x by FSR 3.1 FG (RX_VK_FSR_FG=1)
Method: the same build twice, RX_VK_FSR_FG_HUDLESS=0 and unset, a 6 s right-stick turn, RX_VK_SHOTS + RX_VK_SHOT_MADE of the made frames during it, and the fsr3fi 600-present lines; one run each (a visual check, not timing)
How to reproduce: the steps above, with RX_VK_SHOTS=<dir> RX_VK_SHOT_MADE=1

#1464's mark: this PR @ 93d11850e, RX_VK_FSR_FG_HUDLESS=0 After: this PR @ 93d11850e
Presents made by FSR 3.1 (steady, of 600) 600 600
With the HUD picture 600 600
Hearts in made frames red specks trailing below clean
Minimap a dark streak at its left edge in one frame clean
"A Talk" prompt, X/Y/B clean clean

Baseline: the same build with the switch, so both columns share every other commit; the switch path is #1464's code unchanged.

mask:     vk: fsr3fi: of the last 600 presents 600 made by FSR 3.1, 0 without its inputs (the renderer's own made them); 600 frames with the chain's motion (the skinned draws' own); inputs this frame's 600, the frame before's 0; 600 with the HUD marked
hudless:  vk: fsr3fi: of the last 600 presents 600 made by FSR 3.1, 0 without its inputs (the renderer's own made them); 600 frames with the chain's motion (the skinned draws' own); inputs this frame's 600, the frame before's 0; 600 with the HUD marked

Made frames during the turn, two each. Top row: #1464's mark, this PR @ 93d11850e with RX_VK_FSR_FG_HUDLESS=0. Bottom row: After, this PR @ 93d11850e.

Hearts. Top: #1464's mark, red specks trailing below the hearts. Bottom: After, clean

Minimap. Top: #1464's mark. Bottom: After

A Talk prompt and X/Y/B. Top: #1464's mark. Bottom: After

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_HUDLESS FSR 3.1 interpolates the HUD-less picture and lays the HUD over it (none) on (unset); =0 gives #1464's mark the HUD in FSR 3.1's made frames helps on RTX 3090 Linux; untested on AMD, Intel, Windows on for everyone

Testing

Tested: Linux, RTX 3090, NVIDIA 620.70.06: the A/B above in the game (Kokiri, turning next to the HUD), made frames compared, no Vulkan errors in either log. The person I work for played the build on this PC with FSR 3.1 FG and confirmed the HUD no longer breaks up.

Not tested: python -I -B tests/run_all.py was not run: the checks don't run on this PC. tests/test_fsr3fi_hud_mask.py was updated for the fifth binding and the HUD-less inputs but has not been compiled. Not run on AMD, Intel or Windows; not with DLSS, FSR 4 or XeSS as the upscaler; not with PsychoV35's RGBA16F picture.

Must be tested:

  • python -I -B tests/run_all.py on a PC that runs the checks, expecting fsr3fi hud mask: ok and no new failures (by hand: the author or a reviewer)
  • AMD, Linux (RADV) and Windows: Frame generation 2x by FSR 3.1 FG, Hyrule Field, turn the camera fast, expecting the hearts, icons and minimap whole in every frame and with the HUD marked near 600 in the fsr3fi log line (Test Farm: @Beanstalk amd, linux and windows)
  • Intel, Windows: the same (Test Farm: @Beanstalk intel)

Risks

What could break: FSR 3.1's made frames in play: a HUD element the game draws before its gameplay upscale would be interpolated as scene; a frame that alternates between having the copy and not would reset FSR's history each time (stutter in the made frames).

Turning it off: RX_VK_FSR_FG_HUDLESS=0, or revert the commit.

Compatibility: Nothing changes: no settings, saves or caches; the vk ABI is unchanged.

Issues

See #1310
See #1420

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. (on main @ c7db6c02; the tested build is the same change on b8f3d547, 3 commits earlier, none of them in these files)
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named). (not run on this PC: see Testing)
  • 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.
  • 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 check under tests/ that reads changed source updated in this PR, not weakened. (updated, not yet run)
  • Docs updated.

🤖 Generated with Claude Code

**Type:** fix · **Risk:** medium · **Tested on:** Linux, RTX 3090 · **Needs:** AMD (Windows and Linux), Intel ## TL;DR With AMD FSR 3.1 frame generation, the HUD still breaks up in the made frames when the camera turns, on nightly-429 with #1464: hearts and icons speckle, and pieces of the minimap trail behind it. This PR gives FSR 3.1 the picture from just before the game draws its HUD, so it moves only the scene, then lays the real HUD over each made frame. That's how AMD's SDK is meant to handle a HUD. In the game the HUD stayed clean while turning, where #1464's way left red specks under the hearts. ## Breakdown - **Who it helps:** anyone 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 interpolated frames with the HUD in them, so the frame before's HUD was dragged with the scene, and its colours spread into the gaps a turn opens. - **What changes:** in play, FSR 3.1 interpolates the HUD-less picture #1464 already copies, and AMD's own pass puts this frame's HUD on top. - **What does not change:** menus and movies (no such picture) keep today's path; settings, saves and the shader caches are untouched; the DLSS FG and built-in paths are untouched. - **How it was checked:** an A/B in the game on an RTX 3090, the same build with `RX_VK_FSR_FG_HUDLESS=0` against it: 600 of 600 presents made by FSR 3.1 with the HUD-less picture, no errors, the HUD clean in the made frames. The person I work for played it and confirmed the HUD no longer breaks up. - **What is still open:** a run on AMD and on Intel; `tests/run_all.py` has not been run (see Testing). - **Risk:** medium: every FSR 3.1 made frame in play takes a new path; `RX_VK_FSR_FG_HUDLESS=0` goes back to #1464's. ## Why #1464 marked the HUD in the alpha of the frame FSR 3.1 interpolates, and patched AMD's passes to keep those pixels still. The HUD still breaks up with nightly-429 (a 10 s clip of Hyrule Field turning, FSR 3.1 FG): in the made frames the hearts, the D-pad and Navi icons dissolve into speckles of the scene behind them, the minimap's arrow smears, and part of the minimap trails beside it. Two things the mark can't fix: FSR 3.1 keeps the frame before, HUD and all, as its previous source, and a turn drags that HUD with the scene; and its inpainting fills the holes a turn opens from a pyramid built over the made frame, which already has the HUD written in, so the HUD's colours spread into them. AMD's SDK has a mode for games like this one: give the frame without the HUD as the interpolation source, and the presented frame beside it. The interpolation then never sees a HUD, and the inpainting pass lays the presented frame over the made one wherever the two differ (`HUDLessAttachedFactor`). #1464 already copies exactly that picture (`framegen_hud_before`), so it only had to be handed over. See #1310 (closed by #1464, still seen), #1420, #1464. ## How to reproduce **Seen on:** nightly-429; reported in a clip from a PC other than this one; on this PC (Linux, RTX 3090, NVIDIA 620.70.06) the red specks under the hearts below **Settings and switches:** Frame generation 2x with Frame generation by FSR 3.1 FG (`RX_VK_FSR_FG=1` on NVIDIA), the game's own upscaler **Steps:** Kokiri Forest from the start save, next to Saria ("A Talk" shows), turn the camera with the right stick; or anywhere in Hyrule Field, turning fast **Expected:** the HUD stays still and whole in the made frames **Actual:** in the made frames, scene speckles in the hearts and icons, the minimap's arrow smeared, HUD pixels trailing below the hearts and beside the minimap ## What changed FSR 3.1 is now given AMD's HUD-less colour in play: the picture copied right after the gameplay upscale, cropped as the presented frame, and the presented frame beside it. History resets when a frame switches between the two kinds of source. - shader: `gpu/vk/shaders/fg_hud.comp` writes the copy, cropped as the frame, to a second image (`hudless`) next to the marked source; `fg_hud_comp_spv.h` regenerated. - framegen: `gpu/vk/vk_framegen.cpp` `hud_source()` makes and binds `hud.hudless`; `fsr3fi_frames()` gives it as `in.color` and the presented frame as `in.present` (the marked source with `RX_VK_FSR_FG_HUDLESS=0`, as before). - FSR 3.1 backend: `gpu/vk/vk_fsr3fi.h` `Inputs::present`; `gpu/vk/vk_fsr3fi.cpp` `generate()` sets `hudless_attached_factor` and binds `present` as the inpainting pass's present backbuffer (binding 2), leaves the HUD patches' flags off (no HUD in either source to keep), and resets when the previous source was the other kind. - switch: `RX_VK_FSR_FG_HUDLESS` (`gpu/vk/switches.def`, docs/development.md). - check: `tests/test_fsr3fi_hud_mask.py` follows the mask pass's fifth binding and the HUD-less inputs. ## Measurements **Verdict:** the HUD stays clean in FSR 3.1's made frames where #1464's mark left specks; no cost measured (one extra RGBA8 store per pixel in the existing mask pass), frame times not compared. Hardware: Linux (CachyOS, kernel 7.3.3), RTX 3090, NVIDIA 620.70.06 Scene: Kokiri Forest from the start save next to Saria, 2560x1440 headless, the game's own upscaler, Frame generation 2x by FSR 3.1 FG (`RX_VK_FSR_FG=1`) Method: the same build twice, `RX_VK_FSR_FG_HUDLESS=0` and unset, a 6 s right-stick turn, `RX_VK_SHOTS` + `RX_VK_SHOT_MADE` of the made frames during it, and the `fsr3fi` 600-present lines; one run each (a visual check, not timing) How to reproduce: the steps above, with `RX_VK_SHOTS=<dir> RX_VK_SHOT_MADE=1` | | #1464's mark: this PR @ 93d11850e, `RX_VK_FSR_FG_HUDLESS=0` | After: this PR @ 93d11850e | |---|---|---| | Presents made by FSR 3.1 (steady, of 600) | 600 | 600 | | With the HUD picture | 600 | 600 | | Hearts in made frames | red specks trailing below | clean | | Minimap | a dark streak at its left edge in one frame | clean | | "A Talk" prompt, X/Y/B | clean | clean | Baseline: the same build with the switch, so both columns share every other commit; the switch path is #1464's code unchanged. ``` mask: vk: fsr3fi: of the last 600 presents 600 made by FSR 3.1, 0 without its inputs (the renderer's own made them); 600 frames with the chain's motion (the skinned draws' own); inputs this frame's 600, the frame before's 0; 600 with the HUD marked hudless: vk: fsr3fi: of the last 600 presents 600 made by FSR 3.1, 0 without its inputs (the renderer's own made them); 600 frames with the chain's motion (the skinned draws' own); inputs this frame's 600, the frame before's 0; 600 with the HUD marked ``` Made frames during the turn, two each. Top row: #1464's mark, this PR @ 93d11850e with `RX_VK_FSR_FG_HUDLESS=0`. Bottom row: After, this PR @ 93d11850e. ![Hearts. Top: #1464's mark, red specks trailing below the hearts. Bottom: After, clean](https://git.magicbean.dev/attachments/6a7a4ec6-7dc2-4703-9931-dbf763dd2e71) ![Minimap. Top: #1464's mark. Bottom: After](https://git.magicbean.dev/attachments/87bac40a-7ee3-427d-a21e-22077ba73bee) ![A Talk prompt and X/Y/B. Top: #1464's mark. Bottom: After](https://git.magicbean.dev/attachments/42b5ba4e-495a-4b51-bb3e-cf23ceee2859) ### 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_HUDLESS` | FSR 3.1 interpolates the HUD-less picture and lays the HUD over it | (none) | on (unset); `=0` gives #1464's mark | the HUD in FSR 3.1's made frames | helps on RTX 3090 Linux; untested on AMD, Intel, Windows | on for everyone | ## Testing **Tested:** Linux, RTX 3090, NVIDIA 620.70.06: the A/B above in the game (Kokiri, turning next to the HUD), made frames compared, no Vulkan errors in either log. The person I work for played the build on this PC with FSR 3.1 FG and confirmed the HUD no longer breaks up. **Not tested:** `python -I -B tests/run_all.py` was not run: the checks don't run on this PC. `tests/test_fsr3fi_hud_mask.py` was updated for the fifth binding and the HUD-less inputs but has not been compiled. Not run on AMD, Intel or Windows; not with DLSS, FSR 4 or XeSS as the upscaler; not with PsychoV35's RGBA16F picture. **Must be tested:** - `python -I -B tests/run_all.py` on a PC that runs the checks, expecting `fsr3fi hud mask: ok` and no new failures (by hand: the author or a reviewer) - AMD, Linux (RADV) and Windows: Frame generation 2x by FSR 3.1 FG, Hyrule Field, turn the camera fast, expecting the hearts, icons and minimap whole in every frame and `with the HUD marked` near 600 in the `fsr3fi` log line (Test Farm: @Beanstalk amd, linux and windows) - Intel, Windows: the same (Test Farm: @Beanstalk intel) ## Risks **What could break:** FSR 3.1's made frames in play: a HUD element the game draws before its gameplay upscale would be interpolated as scene; a frame that alternates between having the copy and not would reset FSR's history each time (stutter in the made frames). **Turning it off:** `RX_VK_FSR_FG_HUDLESS=0`, or revert the commit. **Compatibility:** Nothing changes: no settings, saves or caches; the vk ABI is unchanged. ## Issues See #1310 See #1420 ## 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`. (on main @ c7db6c02; the tested build is the same change on b8f3d547, 3 commits earlier, none of them in these files) - [ ] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). (not run on this PC: see Testing) - [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] 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). - [ ] A check under `tests/` that reads changed source updated in this PR, not weakened. (updated, not yet run) - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(vk): FSR 3.1 frame generation interpolates the picture from before the HUD and lays this frame's HUD over it (AMD's HUD-less mode)
Some checks failed
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
CI / Conventional Commit title (pull_request) Successful in 7s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 10s
Third-party parts / As their notes say (pull_request) Successful in 11s
CI / Workflow lint (actionlint) (pull_request) Successful in 15s
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Failing after 8s
93d11850e5
The HUD mark of #1464 still let the HUD smear when the camera turns (#1310): the frame before's HUD
stayed in the interpolation's previous source and was dragged with the scene, and the inpainting
spread the HUD's colours into the holes a turn opens beside it. The picture copied right after the
gameplay upscale is now FSR 3.1's own HUD-less colour: it interpolates the scene alone, and its
inpainting pass lays this frame's HUD over the made frame where the presented frame differs.
RX_VK_FSR_FG_HUDLESS=0 gives the mark as before, for an A/B.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Owner

Tested in game: RTX 3090, NVIDIA 620.70.06, Linux: Kokiri Forest next to Saria, Frame generation 2x by FSR 3.1 FG, turning the camera: A/B against RX_VK_FSR_FG_HUDLESS=0 (#1464's mark), 600/600 presents made by FSR 3.1 with the HUD-less picture, hearts/minimap/prompt clean in the made frames where the mark left red specks under the hearts; also played by hand on the same PC, HUD no longer breaks up.

Tested in game: RTX 3090, NVIDIA 620.70.06, Linux: Kokiri Forest next to Saria, Frame generation 2x by FSR 3.1 FG, turning the camera: A/B against RX_VK_FSR_FG_HUDLESS=0 (#1464's mark), 600/600 presents made by FSR 3.1 with the HUD-less picture, hearts/minimap/prompt clean in the made frames where the mark left red specks under the hearts; also played by hand on the same PC, HUD no longer breaks up.
HumanBean changed title from WIP: fix(vk): FSR 3.1 frame generation interpolates the picture from before the HUD and lays the frame's HUD over it to fix(vk): FSR 3.1 frame generation interpolates the picture from before the HUD and lays the frame's HUD over it 2026-11-18 00:13:56 +00:00
HumanBean deleted branch fix/fsr-fg-hudless 2026-11-18 00:14:08 +00:00
First-time contributor

Follow-up after #1487, testing nightly 464: the HUD fix now works in my visual test with FSR 4 upsaling, but the HUD still moves/shimmers with FSR 4 Native AA at native 1440p. The remaining case appears to involve the FSR 4 Native AA path. Other FSR 4 quality modes have not been isolated in this report.

During a resolution sweep in one session, the log showed:

Internal resolution Output Presents with the HUD marked
1707×960 2560×1440 600/600
2560×1440 2560×1440 0/600, repeatedly
Back down to 1280×720 2560×1440 Returns to 600/600
Back up to 2560×1440 2560×1440 Returns to 0/600, repeatedly
**Follow-up after [#1487](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/1487), testing nightly 464:** the HUD fix now works in my visual test with FSR 4 upsaling, but the HUD still moves/shimmers with **FSR 4 Native AA** at native 1440p. The remaining case appears to involve the FSR 4 Native AA path. Other FSR 4 quality modes have not been isolated in this report. During a resolution sweep in one session, the log showed: | Internal resolution | Output | Presents with the HUD marked | |---|---|---| | 1707×960 | 2560×1440 | 600/600 | | 2560×1440 | 2560×1440 | 0/600, repeatedly | | Back down to 1280×720 | 2560×1440 | Returns to 600/600 | | Back up to 2560×1440 | 2560×1440 | Returns to 0/600, repeatedly |
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!1487
No description provided.