We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Fps cap for autotdp
Make the fps cap selection increment by 5 so we can use 70fps, 80fps and such
No response
Asus ROG ally
The text was updated successfully, but these errors were encountered:
@Devianxe hello,
Can you explain a practical reason for this? As there is not much percieveable difference between 75FPS and 80FPS for example
I prefer to keep UI simple and not force people to click same button like 20 times to switch between 60FPS and 120FPS for example.
Thanks
Sorry, something went wrong.
@Devianxe hello, Can you explain a practical reason for this? As there is not much percieveable difference between 75FPS and 80FPS for example I prefer to keep UI simple and not force people to click same button like 20 times to switch between 60FPS and 120FPS for example. Thanks
Hello mate ,
It's more to fill the gap between 60fps and 90fps.
Yesterday i was playing cod and at the watts set the game could run above 60fps but not reach 90fps.
Added 75FPS limit option for Ally #3485
1f2d186
@Devianxe hello, I think it will be an overkill to have 5FPS steps and it will force you to click button much more times to cycle through them
I have added an extra 75FPS limit to fill your "gap"
Check this build
GHelper.zip
No branches or pull requests
Rules
Is your feature request related to a problem? Please describe
Fps cap for autotdp
Describe the solution you'd like
Make the fps cap selection increment by 5 so we can use 70fps, 80fps and such
Describe alternatives you've considered
No response
Device and Model
Asus ROG ally
Additional information.
No response
The text was updated successfully, but these errors were encountered: