summaryrefslogtreecommitdiff
path: root/src/core
diff options
context:
space:
mode:
authorMerryMage <MerryMage@users.noreply.github.com>2018-08-21 14:35:10 +0100
committerMerryMage <MerryMage@users.noreply.github.com>2018-08-21 14:50:50 +0100
commit3f4fb4b0370d7dc9a0f1e7fc4b006d9f27cb5135 (patch)
tree80688c0dc1b6d386ccc7fd6c9a3f7484c6887794 /src/core
parentbf89a99839abb30e33872b8401eae30cd95e7585 (diff)
perf_stats: Change MAX_LAG_TIME_US to an appropriate value
25us is far too small, and would result in std::this_thread::sleep_for being called with this as a maximum value. This means that a guest application that produces frames instantly would only be limited to 40 kHz. 25ms is a more appropriate value, as it allows for a 60 Hz refresh rate while providing enough slack in the negative region.
Diffstat (limited to 'src/core')
-rw-r--r--src/core/perf_stats.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/core/perf_stats.cpp b/src/core/perf_stats.cpp
index 8e09b9b63..4e5633edb 100644
--- a/src/core/perf_stats.cpp
+++ b/src/core/perf_stats.cpp
@@ -76,7 +76,7 @@ double PerfStats::GetLastFrameTimeScale() {
void FrameLimiter::DoFrameLimiting(microseconds current_system_time_us) {
// Max lag caused by slow frames. Can be adjusted to compensate for too many slow frames. Higher
// values increase the time needed to recover and limit framerate again after spikes.
- constexpr microseconds MAX_LAG_TIME_US = 25us;
+ constexpr microseconds MAX_LAG_TIME_US = 25000us;
if (!Settings::values.toggle_framelimit) {
return;