 |
The legacy cvar for this was com_maxfps |
 |
Great, it would be nice to have it back both as command and menu option. |
|
|
Revision: 7865 ---- Modified : /trunk/framework/Common.cpp Modified : /trunk/framework/Session.cpp |
 |
It used to be that having vsync on would do exactly what you describe. When vsync was off, you would see the actual framerate, which is useful when you want to know the exact fps you're gaining in a scene, either as a mapper or as a player who is adjusting video settings for best fps. How does it work now? |
 |
While vsync can mostly accomplish this feature, end users must also configure the monitor refresh on the driver side or set r_displayRefresh to a specific value in autoexec.cfg (for hardware safety reasons, this cvar value is not archived). Another limitation of vsync is that it falls back to half FPS targets when you miss the threshold. Eg. Go below 60 FPS, then immediately drop to 30. Some drivers support Adaptive vsync modes that don't do this but that's another thing end users have to change in their driver settings. (Admittedly, we might want to consider adding a specific "adaptive" toggle to vsync in the GUI.) To offer a simple summary, this new feature allows you to gain the performance benefits of capping FPS at a specific value without any of the downsides of what vsync does (eg. half FPS targets, buffering latency) ...and without users needing to play with driver settings. |
|
|
I read "activated when the Vsync is Off" as suggesting that there wouldn't be a way to get accurate FPS readings, either with vsync on or off. No worries if that's not the case. |
 |
Hey guys, why 125? Some people have 144 Hz monitors and they complain about such limit =) I'll revert it to 166, since that was the value before change, and merge it to release. |
- Anonymous
