From 3c240bffd38ae9a522a449e5d6b8df41654e8de5 Mon Sep 17 00:00:00 2001 From: Glenn Maynard Date: Sat, 17 May 2003 20:37:18 +0000 Subject: [PATCH] The two-frame hack didn't help any more than the one-frame hack, and it's ugly; remove it. --- stepmania/src/Screen.cpp | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/stepmania/src/Screen.cpp b/stepmania/src/Screen.cpp index 3a78bff6e4..dfbb692cf1 100644 --- a/stepmania/src/Screen.cpp +++ b/stepmania/src/Screen.cpp @@ -79,19 +79,13 @@ void Screen::Update( float fDeltaTime ) * not quite finishing their tweens. * * Let's delay all messages that have a non-zero time an extra frame. - * - * XXX: For some reason, I had to make this delay messages for *two* frames to - * make this effect go away. (SMMAX2 menu header tweens.) I'm not sure why. */ if(m_QueuedMessages[i].fDelayRemaining > 0.0001f) { m_QueuedMessages[i].fDelayRemaining -= fDeltaTime; m_QueuedMessages[i].fDelayRemaining = max(m_QueuedMessages[i].fDelayRemaining, 0.0001f); } else { - /* Two 0.00008 delays add up to at least one 0.0001 delay, but don't count - * Update(0)s. This is hacky, until I figure out why the second frame - * delay is needed ... */ - m_QueuedMessages[i].fDelayRemaining -= max(fDeltaTime, 0.00008f); + m_QueuedMessages[i].fDelayRemaining -= fDeltaTime; } }