diff options
author | Patric Stout <truebrain@openttd.org> | 2021-02-17 15:31:09 +0100 |
---|---|---|
committer | Patric Stout <github@truebrain.nl> | 2021-02-19 10:43:15 +0100 |
commit | fa170b9ace1a2f45833627676b0106ee13914bd4 (patch) | |
tree | de0471ae9fcbd98799a1626e178758d7edbd01e7 /src/settings_type.h | |
parent | eb9b1ad68d84ddbebb3d9e50f3ec8d3ad195c75c (diff) | |
download | openttd-fa170b9ace1a2f45833627676b0106ee13914bd4.tar.xz |
Feature: configurable refresh-rate and change default to 60fps
Most modern games run on 60 fps, and for good reason. This gives
a much smoother experiences.
As some people have monitors that can do 144Hz or even 240Hz, allow
people to configure the refresh rate. Of course, the higher you
set the value, the more time the game spends on drawing pixels
instead of simulating the game, which has an effect on simulation
speed.
The simulation will still always run at 33.33 fps, and is not
influences by this setting.
Diffstat (limited to 'src/settings_type.h')
-rw-r--r-- | src/settings_type.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/settings_type.h b/src/settings_type.h index 3c325a0cc..11298cfa7 100644 --- a/src/settings_type.h +++ b/src/settings_type.h @@ -147,6 +147,7 @@ struct GUISettings { byte starting_colour; ///< default color scheme for the company to start a new game with bool show_newgrf_name; ///< Show the name of the NewGRF in the build vehicle window bool auto_remove_signals; ///< automatically remove signals when in the way during rail construction + uint16 refresh_rate; ///< How often we refresh the screen (time between draw-ticks). uint16 console_backlog_timeout; ///< the minimum amount of time items should be in the console backlog before they will be removed in ~3 seconds granularity. uint16 console_backlog_length; ///< the minimum amount of items in the console backlog before items will be removed. |