You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We already have unlimited FPS thanks to Merlin's and others Framerate fixes. Still, most users can't really benefit for them because they need to be told by the server that they can uncap their FPS.
I have done this multiple times in my own server (we have a FPS limit of 144, but players will get only to 100fps until we tell them they can update their fps_limit via the console).
Describe the solution you'd like
Change CClientVariables.cpp default fps_limit value from 100 to 0, so it will be uncapped by default.
Describe alternatives you've considered
Change CClientVariables.cpp default fps_limit value from 100 to 144, since most monitors won't have more than 144hz, and most "hardcore" gamers will have no problem changing the fps_limit value by themselves if needed.
Having FPS higher than 200 will cause some problems (at over 250fps your ped starts to warp while aiming), so maybe fps_limit=200 its more logical (165hz monitors are also kinda popular).
Additional context
No response
Security Policy
I have read and understood the Security Policy and this issue is not about a cheat or security vulnerability.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We already have unlimited FPS thanks to Merlin's and others Framerate fixes. Still, most users can't really benefit for them because they need to be told by the server that they can uncap their FPS.
I have done this multiple times in my own server (we have a FPS limit of 144, but players will get only to 100fps until we tell them they can update their fps_limit via the console).
Describe the solution you'd like
Change
CClientVariables.cpp
default fps_limit value from 100 to 0, so it will be uncapped by default.Describe alternatives you've considered
Change
CClientVariables.cpp
default fps_limit value from 100 to 144, since most monitors won't have more than 144hz, and most "hardcore" gamers will have no problem changing the fps_limit value by themselves if needed.Having FPS higher than 200 will cause some problems (at over 250fps your ped starts to warp while aiming), so maybe fps_limit=200 its more logical (165hz monitors are also kinda popular).
Additional context
No response
Security Policy
The text was updated successfully, but these errors were encountered: