From d4f68cb1647ca87e5364431f09ab38b3178ed3cd Mon Sep 17 00:00:00 2001 From: Jordan Woyak Date: Mon, 27 Oct 2025 05:25:25 -0500 Subject: [PATCH] HW/VideoInterface: Selectively throttle on "VBlank" based on "Immediate XFB" being enabled. --- Source/Core/Core/HW/VideoInterface.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Source/Core/Core/HW/VideoInterface.cpp b/Source/Core/Core/HW/VideoInterface.cpp index c0f46bed358..f97852df7aa 100644 --- a/Source/Core/Core/HW/VideoInterface.cpp +++ b/Source/Core/Core/HW/VideoInterface.cpp @@ -886,10 +886,10 @@ void VideoInterfaceManager::EndField(FieldType field, u64 ticks) // Note: OutputField above doesn't present when using GPU-on-Thread or Early/Immediate XFB, // giving "VBlank" measurements here poor pacing without a Throttle call. - // If the user actually wants the data, we'll Throttle to make the numbers nice. - const bool is_vblank_data_wanted = g_ActiveConfig.bShowVPS || g_ActiveConfig.bShowVTimes || - g_ActiveConfig.bLogRenderTimeToFile || - g_ActiveConfig.bShowGraphs; + // We'll throttle so long as Immediate XFB isn't enabled. + // That setting intends to minimize input latency and throttling would be counterproductive. + // The Rush Frame Presentation setting is handled by Throttle itself. + const bool is_vblank_data_wanted = !g_ActiveConfig.bImmediateXFB; if (is_vblank_data_wanted) m_system.GetCoreTiming().Throttle(ticks);