Fps max: Difference between revisions
Jump to navigation
Jump to search
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]
(it's just a simple cvar lol, doesn't need all the syntax explanations and examples, the bug notice is just duplicate of information above) |
(update to new reference template) |
||
| Line 1: | Line 1: | ||
{{LanguageBar}} | {{LanguageBar}} | ||
{{This is a|console variable|name=fps_max|engine=GoldSrc|engine1=Source|engine2=Source 2}} | {{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){{ | 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}}. | ||
| Line 8: | Line 8: | ||
{{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}}}} | {{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= | |||
{{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}} | |||
}} | |||
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 FPSNote: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
| References | ||
|---|---|---|
|