FSR 3.1 FG: HUD-less mode (RX_VK_FSR_FG_HUDLESS=1) outputs repeated real frames instead of interpolated frames #1732
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1732
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
With FSR 3.1 Frame Generation enabled (
2x-4xorAuto), the FPS counter increases as expected (e.g.Base 61 -> 240 FPS), andlongshot_log.txtconfirmsfsr3fiis running (600 made by FSR 3.1,600 with the HUD marked), but visually every generated frame is identical to the real game frame (no real motion interpolation - looks like the base framerate).NVIDIA DLSS FG works smoothly on the exact same setup.
Environment
nightly-464-310e7c9d(LongshotBuilder v3.0.0)3440x1440(internal2580x1080),hdr=1(Expanded HDR), Upscaler:NVIDIA DLSSorAMD FSR 3.1, Frame Gen:FSR 3.1 FG(4x)A/B Isolation Results
RX_VK_FSR_FG_HUDLESS=1): FPS counter shows240 FPS, logs show600 made by FSR 3.1+600 with the HUD marked, but visually frames are duplicated / not interpolated.RX_VK_FSR_FG_HUDLESS=0: Interpolation immediately becomes smooth at 240 FPS, confirmingfsr3fioptical flow + motion vectors work properly, though the HUD smears/artifacts (as noted invk_framegen.cpphud_sourcecomments forkHudMaskwithout HUD-less).Suspected Root Cause
In
gpu/vk/shaders/fg_hud.comp+scripts/fsr3_shaders.py(FI_PATCHES#4):fg_hud.compchecks exact equalityif (scene == drawn) return shown;, otherwise writessrgb(scene)intohudless.ffx_frameinterpolation_inpainting.h(FI_PATCHES#4),fStaticFactoris forced to1.0fwheneverabs(fCurrentInterpolationSource - fPresentColor) > 0.0.hud.before(B10G11R11) andhud.afterdiffer across the frame (orsrgb(scene)differs by >= 1 LSB fromshown),P_FI_INPAINTINGoverwrites the entire interpolated frame withfPresentColor(shown), turning every generated frame into a copy of the real frame.Suggested Fix
FI_PATCHES#4 /hudlessstatic overlay with a small tolerance or only applyfPresentColorwhere the HUD mask (hud.sourcealpha) actually detected post-upscale UI, orscene != drawn/srgb(scene) != showntriggers across non-HUD pixels infg_hud.comp(e.g. withhdr=1or post-upscale passes).This looks like the same problem as #1310 (Game: FSR3.1 Framegen UI Glitching in Camera Motion), so I'm closing this one to keep the discussion in one place.
The reported symptom is precisely the repeated real frames from FSR 3.1 HUD-less interpolation that followed the HUD handling fix tracked by this issue and was fixed by PR #1538.
If it's different, say how and a maintainer will reopen it.
This is not fixed by PR #1538 — my build (
nightly-464-310e7c9d, built 2026-11-18, andLongshotBuilder v3.0.0) already includes PR #1538 (fg_hud.comphashudless_colourreturningshownwhenscene == drawn), yet the bug still reproduces 100% of the time on Windows 11 + NVIDIA RTX 5070 Ti.Note that PR #1538 itself listed
Tested on: Linux, RTX 3090 · Needs: AMD (Linux or Windows), Windows NVIDIA.Specifically, even with #1538 applied:
RX_VK_FSR_FG_HUDLESS=1, FSR 3.1 FG (4x,3440x1440,hdr=1Expanded HDR,NVIDIA DLSSorAMD FSR 3.1upscaler) logs600 made by FSR 3.1+600 with the HUD marked, but visually outputs repeated real frames (no interpolation).RX_VK_FSR_FG_HUDLESS=0immediately restores smooth 240 FPS interpolation (with the expectedkHudMask-only HUD smearing from #1310).So
scene != drawninfg_hud.comp(or a mismatch betweenhudlessandshown) is still triggeringFI_PATCHES#4 (fStaticFactor = 1.0f) across non-HUD pixels on Windows NVIDIA /hdr=1even after #1538. Please reopen this issue for investigation.Update: I just tested the official
v3.0.0release (rc/v3.0.0) with default settings (noRX_VK_FSR_FG_HUDLESSoverride), and FSR 3.1 Frame Generation now interpolates smoothly (600 made by FSR 3.1,600 with the HUD marked,720 frames shown on time).So this is indeed resolved in
v3.0.0— keeping the issue closed is fine. Thanks!