Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auto-fps limiter with vsync + VRR #2

Open
aufkrawall opened this issue Sep 7, 2024 · 2 comments
Open

auto-fps limiter with vsync + VRR #2

aufkrawall opened this issue Sep 7, 2024 · 2 comments

Comments

@aufkrawall
Copy link

aufkrawall commented Sep 7, 2024

Competitor product has a feature that automatically limits fps when vsync + VRR are used at the same time. This is done to avoid additional input lag, which occurs when frame rate is capped by vsync, as even with VRR this causes additional queued frames in vsync backbuffer. Many games unfortunately don't offer an fps limiter that's freely configurable to the user.

Thus it would be nice if Anti-Lag 2 had that feature too. It should also work with FSR 3 FG. Formula to determine the fps limit could be something like ~5% below potential vsync limit, e.g. 138fps with 144Hz. As soon as Anti-Lag 2, vsync and VRR are active at the same time, this auto-limiter should kick in.

And slightly OT: Please make driver-feature Chill finally work better, which means:
-not turn itself off under very low GPU load or other circumstances
-make it work combined with driver anti-lag
-make it work with FSR 3 FG

Driver FRTC limiter is not an option, as also your own tool Frame Latency Meter testifies that it introduces absurd input lag, unlike Chill.

Thanks!

@gareththomasamd
Copy link

Thanks for your input here, appreciated.

Chill is turned off under low GPU load as it causes load times to go up. Perhaps we could add some control here via an API if there is demand for it.

Regarding the other two points on Chill: noted :)

@aufkrawall
Copy link
Author

Thanks a lot for your reply @gareththomasamd .

Chill is turned off under low GPU load as it causes load times to go up. Perhaps we could add some control here via an API if there is demand for it.

That would be great. It's just my 2 cents, but I personally would argue that a bit longer loading times would even be the lesser evil vs. completely losing Chill fps limiter functionality in some situations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants