Fps max: Difference between revisions

Latest revision as of 22:53, 4 September 2025

fps_max is a console variable available in all GoldSrc, Source, and Source 2 games. This is a ConVar where you can define your frame rate limit. It is recommended that you limit them to the refresh rate of your monitor, because any frame rate above that is wasted, and could cause the monitor to have screen tearing issues, causing the systems to make coil whine noises due to higher power draw. Furthermore, having more than around 1000+FPS in a Source games (or 100+ in GoldSrc) will cause timing-related issues (such as the game running faster than normal) and potentially causing the game to stutter (or cause the servers to teleport you back where you should be)^[1].

Note:Default: 300 FPS, 400FPS in

CS:GO and

Team Fortress 2 branch.

Note:Using value 0 disables FPS cap in Source/Source 2, while in GoldSrc it will make game run at 1 FPS

Note:On listen servers, going above 1000 FPS may cause pseudo-speedhacks, where time seems to have sped up. It should not happen on dedicated servers.^[confirm]

References

1.	3klikphilip (2023), 1000 FPS in CS:GO?????. YouTube. Retrieved on 4 September, 2025.

@@ Line 1: / Line 1: @@
-{{langsp}}
+{{LanguageBar}}
-This is a [[ConVar]] you can enter in to limit your frames per second. It is recommended that you limit your frames to the refresh rate of your monitor, because any frame rate above that is wasted. Furthermore, having more than around 1000+FPS may cause the timing-related issues (such as the game running faster than normal) and potentially causing the game to stutter (or cause the servers to teleporting you back where you should be){{ref|1}}.
+{{This is a|console variable|name=fps_max|engine=GoldSrc|engine1=Source|engine2=Source 2}}
-----
+This is a [[ConVar]] where you can define your '''frame rate limit'''. It is recommended that you limit them to the refresh rate of your monitor, because any frame rate above that is wasted, and could cause the monitor to have screen tearing issues, causing the systems to make coil whine noises due to higher power draw. Furthermore, having more than around 1000+FPS in a {{src|4}} games (or 100+ in {{gldsrc|4}}) will cause timing-related issues (such as the game running faster than normal) and potentially causing the game to stutter (or cause the servers to teleport you back where you should be){{cite|1}}.
-{{syntax|fps_max <frames per second>}}
-{{note|Default: 300 FPS, 400FPS in {{csgo|4|nt=CS:GO}}.}}
-{{CCExample|If you wanted 85 frames per second, you would type in the console: |fps_max 85}}
-Quotation marks around strings are not always required, but should be used to ensure that special characters, such as spaces and semicolons, are not misinterpreted. For number-only strings, quotation marks should not be used.
-== References ==
+{{note|Default: 300 FPS, 400FPS in {{csgo|4|nt=CS:GO}} and {{tf2branch|2}}.}}
-<ol>
+{{note|Using value 0 disables FPS cap in Source/Source 2, while in GoldSrc it will make game run at 1 FPS}}
-<li> '''3klikphilip''' - {{youtube|page=video|5GneP6MuVOk|1000 FPS in CS:GO????}}<br>But something strange was going on. In some areas, particularly around B and inside the tunnels, my footstep sounds got faster than normal,<br>and while it could have just been the INCREDIBLE framerate I was getting, I could swear I was moving faster, too!
+{{note|On listen servers, going above 1000 FPS may cause pseudo-speedhacks, where time seems to have sped up. It should not happen on dedicated servers.{{confirm}}}}
-</ol>
+{{References|1=
+{{ref2|cite id=1|author=[https://www.youtube.com/@3kliksphilip 3klikphilip]|title=1000 FPS in CS:GO?????|website=YouTube|url = https://youtu.be/5GneP6MuVOk|year=2023|access-date=4 September, 2025}}
+}}

Fps max: Difference between revisions

Latest revision as of 22:53, 4 September 2025

References

Navigation menu

Search