From 8d6493fae4e466c075fce895fade3878f57c73f4 Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Tue, 1 Aug 2023 17:43:32 +0200 Subject: [PATCH] Initialize View Frame Time estimates to match 120 FPS This prevents the estimation from being extremely high (close to 100,000 FPS) until enough time has passed to display an accurate estimation. (cherry picked from commit 15b31f0891fde06da4fa617276705b1d6404b2dd) --- editor/plugins/node_3d_editor_plugin.cpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/editor/plugins/node_3d_editor_plugin.cpp b/editor/plugins/node_3d_editor_plugin.cpp index f2722ec622a..e175f3330f9 100644 --- a/editor/plugins/node_3d_editor_plugin.cpp +++ b/editor/plugins/node_3d_editor_plugin.cpp @@ -2832,8 +2832,9 @@ void Node3DEditorViewport::_notification(int p_what) { fps_label->set_visible(show_fps); RS::get_singleton()->viewport_set_measure_render_time(viewport->get_viewport_rid(), show_fps); for (int i = 0; i < FRAME_TIME_HISTORY; i++) { - cpu_time_history[i] = 0; - gpu_time_history[i] = 0; + // Initialize to 120 FPS, so that the initial estimation until we get enough data is always reasonable. + cpu_time_history[i] = 8.333333; + gpu_time_history[i] = 8.333333; } cpu_time_history_index = 0; gpu_time_history_index = 0;