FSR AA... VSYNC...XEFG...OPTISCALER #2204
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
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2204
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?
The idea
Hello, my friend. Thank you so much for all your hard work!
Since the latest game update, I haven't experienced any crashes or freezes at all, and the loading speed has improved significantly. The only remaining issues are a low frame rate and occasional stuttering.
I’d like to request a few features for future updates:
Support for FSR AA (such as versions 2.1 and 4.1.2).
Support for OptiScaler—it’s an excellent mod.
Integration of XeFG, as it performs significantly better than FSR.
The addition of V-Sync; many users, myself included, have 60Hz monitors. When Frame Generation is enabled and the frame rate climbs to 80–90 FPS, it causes screen tearing/judder. Could you please allow V-Sync and Frame Generation to be enabled simultaneously?
The OptiScaler mod could actually address all of these points—it includes V-Sync, various Frame Generation methods, and upscaling technologies like FSR, XeFG, XeSS, and more (it even supports DLSS).
Thanks again for all your efforts!
Anything else
No response
game doesnt have fsr4 for rdna 2 cards like me..rx6700xt
anti aliasing is not good
plz add xefg
+1 for XeSS. I have a 7900 XT and it looks better than FSR 3 (and 4 on my card) for upscaling in motion.
Thanks for the report. Reports of the same problem are now collected in #1007, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #1007 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.