FrameGen and FSR causes blur and ghosting while moving #1635
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#1635
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?
Hookshot version
v2.0.12
What kind of problem
Graphics (missing, black or wrong-coloured things, lighting, flicker)
What happened
As in the video attached, when having FSR 2x on, UI blurs and Link has a ghost trail.
Where in the game
Zora's Domain
How often
Every time
Graphics card and driver version
RX 9060XT, 26.10.1
CPU, RAM and operating system
Ryzen 7 7700, 32GB DDR5, Windows 11 Pro 26H2
Changes from the defaults
No response
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
hookshot_log.1.txt
hookshot_log.2.txt
hookshot_log.3.txt
hookshot_log.4.txt
hookshot_log.txt
Screenshots or video
https://github.com/user-attachments/assets/e799cd47-3bfe-497a-8f49-7db52978ba9a
Before you send it
Same issue on my 4060
same .. even without fsr for me.. when it uses games own thing
https://github.com/user-attachments/assets/f011e836-dd19-413c-b2a4-83c06e224b31
disabling framegen or setting it to auto fixed it for me.
Disabling framegen atill has the same ghosting might try auto later
I can confirm this issue. Turning off framegen fixes it for me. Something broke for sure.
@NotRexed the ghosting and flickering from the videos are still there
Same problem rtx 4060 / i5-4460
A likely reason this shows only at 2x: since v2.0.12, Frame generation 2x uses AMD's FSR 3.1 frame interpolation, while 3x and up use the older interpolation (gpu/vk/vk_fsr3fi.cpp). The duplicates closed into this issue fit that: HUD smearing, Link's ghost trail, and a large semi-transparent rectangle, all at 2x only (#1713, #1716, #1725). Workaround until it's fixed: put
RX_VK_FSR_FG=0in hookshot_env.txt (beside hookshot.exe) to use the older interpolation at 2x, or turn frame generation off or to Auto.Workaround: Disable the in-game Frame Generation and use NVIDIA Smooth Motion instead. This eliminates the large semi-transparent rectangular artifact and significantly reduces the ghosting seen with 2× Frame Generation.
Try deleting the game folder and re-compile from scratch. This problem appeared after I updated to the last 2 versions along with DLSS scaling not appearing in the menu (even tho the option was checked before re-compiling). Both fixed after a brand new recompile and I tested frame gen with auto, 2x and 3x frame + game's upscaler, dlss and fsr. There is no HUD ghosting anymore.
Another Discord report fits this: a visual glitch while moving on an RTX 3080 Ti, "not in v2.0.11". FSR 3.1 interpolation at frame generation 2x came in v2.0.12. If you see this too, please say your Frame generation setting and Frame rate cap, and whether
RX_VK_FSR_FG=0or frame generation off makes it go away.Another Discord report after updating (yabb2014): the HUD (hearts, minimap, item) turns semi-transparent and ghosts while running. That's frame generation interpolating the HUD. If you see this, does it go away with Frame generation off (or with
RX_VK_FSR_FG=0at 2x)?Confirmed by a second player on Discord: the HUD ghosting goes away with Frame generation off, and stays gone after turning it back on. So it's frame generation interpolating the HUD; the off/on cycle clearing it is also a clue (a state that frame generation keeps until it's reset).
Narrowed down by a third player on Discord: the HUD ghosting happens only with Frame generation 2x and Frame pacing on. Turning Frame pacing off, or setting Frame generation to 3x, makes it go away. So it's in the paced 2x path (the FSR 3.1 interpolation with frame pacing; see also #1702 on its timing).