The minimum value was increased from 30 to 35 to reflect the lowest
value you can actually use in `vid_maxfps`. Values lower than 35
are silently clamped to 35.
The maximum value is chosen to cater to the fastest commercially
available display as of writing (500 Hz).
Being able to specify maximum FPS with a more precise slider has
several benefits:
- This adds support for monitors with less common refresh rates
(138 Hz, 165 Hz, ...).
- This adds support for monitors with very high refresh rates
(240 Hz or more).
- This allows catering to variable refresh rate setups with a FPS cap
chosen to avoid V-Sync input lag, while also avoiding tearing.
For example, choosing a FPS cap of 117 on a 120 Hz display will prevent
the display from reaching its maximum refresh rate.
More information: https://blurbusters.com/howto-low-lag-vsync-on/
- The value no longer displays a "Unknown" if customized in the console
using the `vid_maxfps` cvar.
This is mainly for new games which have been designed for hardware rendering.
Note that this does not remove the software renderer's code - all it does is to disable the vid_rendermode CVAR by turning it into a static constant with the value 4.
