Game: FSR3.1 Framegen UI Glitching in Camera Motion #1310

Open
opened 2026-11-17 02:37:18 +00:00 by EvergaolBirb · 7 comments

Longshot version

nightly-399-f88e6e3a

Channel

Nightly

What kind of problem

Graphics (missing, black or wrong-coloured things, lighting, flicker)

What happened

FSR3.1 Framegen when turned on (2x or more) causes the UI to glitch. Also tested with Build-in FG and MAKO FrameGen (External) and both doesn't affect the UI.

I've attached a Youtube Video.

Note: Also noticed an input lag on Gamepad with FSR3.1 FG, please add support for AMD Anti Lag 2 (Already included with users that have Goverlay If I'm not mistaken).

Where in the game

Anywhere

How often

Every time

Graphics card and driver version

RX 6700 XT, MESA 26.2.6

CPU, RAM and operating system

Ryzen 5 5600, 16GB, CachyOS

Changes from the defaults

No response

longshot_log.txt

longshot_log

Screenshots or video

https://youtu.be/bFm7joqZzpI

Before you send it

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### Longshot version nightly-399-f88e6e3a ### Channel Nightly ### What kind of problem Graphics (missing, black or wrong-coloured things, lighting, flicker) ### What happened FSR3.1 Framegen when turned on (2x or more) causes the UI to glitch. Also tested with Build-in FG and MAKO FrameGen (External) and both doesn't affect the UI. I've attached a Youtube Video. Note: Also noticed an input lag on Gamepad with FSR3.1 FG, please add support for AMD Anti Lag 2 (Already included with users that have Goverlay If I'm not mistaken). ### Where in the game Anywhere ### How often Every time ### Graphics card and driver version RX 6700 XT, MESA 26.2.6 ### CPU, RAM and operating system Ryzen 5 5600, 16GB, CachyOS ### Changes from the defaults _No response_ ### longshot_log.txt [longshot_log](/attachments/939785d1-fb4f-47f5-ad5d-85d7db2fe8b8) ### Screenshots or video https://youtu.be/bFm7joqZzpI ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Collaborator

Possibly related, for context:

  • issue #1236 Game: FSR 3.1 frame generation shows swinging limbs as see-through copies in made frames — FSR 3.1 frame-generation motion artifacts, but character limb ghosting rather than UI distortion
  • issue #1075 Game: DLSS Frame Generation causes artifacts in HUD — HUD artifacts under frame generation, but reported with DLSS on NVIDIA
  • PR #1103 feat(vk): FSR 3.1 frame generation for everyone: FSR 3.1 FG on Frame generation by, any multiplier and Auto, the HUD kept still, actor motion — Merged FSR 3.1 frame-generation implementation; report is on nightly-399 after this change
Possibly related, for context: - issue #1236 Game: FSR 3.1 frame generation shows swinging limbs as see-through copies in made frames — FSR 3.1 frame-generation motion artifacts, but character limb ghosting rather than UI distortion - issue #1075 Game: DLSS Frame Generation causes artifacts in HUD — HUD artifacts under frame generation, but reported with DLSS on NVIDIA - PR #1103 feat(vk): FSR 3.1 frame generation for everyone: FSR 3.1 FG on Frame generation by, any multiplier and Auto, the HUD kept still, actor motion — Merged FSR 3.1 frame-generation implementation; report is on nightly-399 after this change
Collaborator

From Discord:

Additional affected system and evidence: Longshot 3.0.0 RC6 on Windows 10 LTSC; Radeon RX 9070 with Adrenalin 26.10.1; Ryzen 5 5600X, 64 GB DDR4-3200. Reporter says enabling FSR 3.1 instead of the built-in frame generator, with no DLSS, causes HUD artifacts as the camera moves, anywhere. Attached longshot_log.txt and video 2026-11-16_22-52-45.mp4. Log identifies v3.0.0-rc.6 and 2560×1440 output.

From [Discord](https://discord.com/channels/1569849200047427645/1572104405745148034/1572104405745148034): Additional affected system and evidence: Longshot 3.0.0 RC6 on Windows 10 LTSC; Radeon RX 9070 with Adrenalin 26.10.1; Ryzen 5 5600X, 64 GB DDR4-3200. Reporter says enabling FSR 3.1 instead of the built-in frame generator, with no DLSS, causes HUD artifacts as the camera moves, anywhere. Attached longshot_log.txt and video 2026-11-16_22-52-45.mp4. Log identifies v3.0.0-rc.6 and 2560×1440 output.
Collaborator

From Discord:

Additional affected system/evidence from Discord: Nightly 396 on Windows 11, Radeon RX 9070 XT (Adrenalin 26.11.1), Ryzen 7 5700X3D, 32 GB RAM, 2560×1440. Reporter compares FSR 3.1 FG with native FG and observes pronounced HUD ghosting around Link's hearts and item; videos attached in Discord. No longshot_log.txt was supplied yet.

From [Discord](https://discord.com/channels/1569849200047427645/1572131574311419944/1572137005352226866): Additional affected system/evidence from Discord: Nightly 396 on Windows 11, Radeon RX 9070 XT (Adrenalin 26.11.1), Ryzen 7 5700X3D, 32 GB RAM, 2560×1440. Reporter compares FSR 3.1 FG with native FG and observes pronounced HUD ghosting around Link's hearts and item; videos attached in Discord. No longshot_log.txt was supplied yet.

Additional affected hardware on rc.7: Radeon RX 5700 XT 8 GB (RDNA 1), Windows 11 build 26300, AMD proprietary driver 26.10.1. CPU Ryzen 7 5700X3D, 32 GB RAM. Longshot v3.0.0-rc.7, source e5cea4aa from the game log; output 2560×1440.

I see the fixed HUD/menu overlay elements repeatedly glitter/flicker or glitch when moving the camera left and right with FSR 3.1 frame generation. I can see it anywhere rather than at one specific location; horizontal camera movement is the trigger.

Current saved settings show 2× frame generation with FSR 3.1 FG, the report concerns the screen-fixed UI during camera motion, rather than the separate character-limb ghosting report.

I have not yet supplied a captured video, a comparison against Built-in FG / FG Off at the same spot, or a test on current main. Please treat this as an additional player observation on RDNA 1 / Windows, not as a controlled A/B result or a diagnosed cause.

Additional affected hardware on rc.7: **Radeon RX 5700 XT 8 GB (RDNA 1), Windows 11 build 26300, AMD proprietary driver 26.10.1**. CPU Ryzen 7 5700X3D, 32 GB RAM. Longshot v3.0.0-rc.7, source `e5cea4aa` from the game log; output 2560×1440. I see the fixed HUD/menu overlay elements repeatedly glitter/flicker or glitch when moving the camera left and right with FSR 3.1 frame generation. I can see it anywhere rather than at one specific location; horizontal camera movement is the trigger. Current saved settings show 2× frame generation with FSR 3.1 FG, the report concerns the screen-fixed UI during camera motion, rather than the separate character-limb ghosting report. I have not yet supplied a captured video, a comparison against Built-in FG / FG Off at the same spot, or a test on current main. Please treat this as an additional player observation on RDNA 1 / Windows, not as a controlled A/B result or a diagnosed cause.
Collaborator

From Discord:

Additional affected system and video: the reporter is on v3.0.0-rc.7 and observes HUD smearing with FSR 3.1 frame generation in the temple area shown in the attached video; they say it does not occur with built-in frame generation. The video shows gameplay and the RC7 version screen. GPU/driver, OS, CPU/RAM, exact frame-generation settings and log were not provided.

From [Discord](https://discord.com/channels/1569849200047427645/1572184018353520731/1572184018353520731): Additional affected system and video: the reporter is on v3.0.0-rc.7 and observes HUD smearing with FSR 3.1 frame generation in the temple area shown in the attached video; they say it does not occur with built-in frame generation. The video shows gameplay and the RC7 version screen. GPU/driver, OS, CPU/RAM, exact frame-generation settings and log were not provided.
Collaborator

From Discord:

Additional affected system from Discord: Longshot v3.0.0-rc.7 and nightly 403; Windows 11 25H2, Radeon RX 7800 XT, driver 26.10.1, Ryzen 5 7600X, 32 GB DDR5. Reporter says HUD is blurry/twitchy during camera motion or fast movement anywhere, every time, and has now confirmed it occurs only when FSR 3.1 is enabled. Original longshot_log.txt and video are attached to the Discord report. The log contains no HOS_THREAD_TIMES or RX_VK_PASS_TIMING profiling measurements. Exact graphics settings and a performance profile remain unknown.

From [Discord](https://discord.com/channels/1569849200047427645/1572236687713640488/1572236687713640488): Additional affected system from Discord: Longshot v3.0.0-rc.7 and nightly 403; Windows 11 25H2, Radeon RX 7800 XT, driver 26.10.1, Ryzen 5 7600X, 32 GB DDR5. Reporter says HUD is blurry/twitchy during camera motion or fast movement anywhere, every time, and has now confirmed it occurs only when FSR 3.1 is enabled. Original longshot_log.txt and video are attached to the Discord report. The log contains no HOS_THREAD_TIMES or RX_VK_PASS_TIMING profiling measurements. Exact graphics settings and a performance profile remain unknown.
Collaborator

From Discord:

Additional affected system and evidence from Discord: Longshot v3.0.0-rc.7 on Windows; AMD Ryzen 3 2200G, 16 GB 2400 MHz RAM, NVIDIA GeForce GTX 1050 Ti, driver 582.78. The reporter says FSR 3.1 FG causes twitching/glitching of the HUD and the sword sheath on Link's back, unlike built-in FG; supplied a video (Longshot_2026-11-17_16-31-49.mp4). Exact graphics settings, OS, and longshot_log.txt are not available in the thread.

From [Discord](https://discord.com/channels/1569849200047427645/1572258853616361592/1572258853616361592): Additional affected system and evidence from Discord: Longshot v3.0.0-rc.7 on Windows; AMD Ryzen 3 2200G, 16 GB 2400 MHz RAM, NVIDIA GeForce GTX 1050 Ti, driver 582.78. The reporter says FSR 3.1 FG causes twitching/glitching of the HUD and the sword sheath on Link's back, unlike built-in FG; supplied a video (Longshot_2026-11-17_16-31-49.mp4). Exact graphics settings, OS, and longshot_log.txt are not available in the thread.
Sign in to join this conversation.
No milestone
No project
No assignees
3 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#1310
No description provided.