mirror of
https://github.com/wesnoth/wesnoth
synced 2025-04-26 19:06:22 +00:00
b859060627
The pre-processing for --max-fps was basically identical to what draw_manager::get_frame_length does. This replaces the draw_delay preference with a new refresh_rate preference that more accurately describes what is being set. video::current_refresh_rate will now take this preference into account, meaning the build info report will correctly report player-set FPS limits. The Limit FPS option in the prefs UI was also removed. When it was first introduced (cca79afe4b263187a54b73042a9bc7eaa46986e7) it specifically affected the map rendering code, not the rendering pipeline as a whole. With the 1.17 rendering refactor, this is no longer the case, and so its current usage as the lower bound for frametime calculations did nothing (all it did was change the lower bound from 0 to -1 when enabled). It might be worth adding a slider to the UI to dynamically set max fps, but that's a separate change.