actions/itgmania212121
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

fix occasional one-frame glitches

Browse Source
This commit is contained in:
Glenn Maynard
2002-12-29 23:37:41 +00:00
parent bbc7fa5f81
commit c8b16777af
2 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stepmania/src/ScreenGameplay.cpp
-2
View File
@@ -474,8 +474,6 @@ ScreenGameplay::ScreenGameplay()
for( int i=0; i<30; i++ ) for( int i=0; i<30; i++ )
this->SendScreenMessage( ScreenMessage(SM_User+i), i/2.0f ); // Send messages to we can get the introduction rolling this->SendScreenMessage( ScreenMessage(SM_User+i), i/2.0f ); // Send messages to we can get the introduction rolling
} }
Update(0);
} }
ScreenGameplay::~ScreenGameplay() ScreenGameplay::~ScreenGameplay()
stepmania/src/ScreenManager.cpp
+6 -1
View File
@@ -232,7 +232,12 @@ Screen* ScreenManager::MakeNewScreen( CString sClassName )
else else
RageException::Throw( "Invalid Screen class name '%s'", sClassName.GetString() ); RageException::Throw( "Invalid Screen class name '%s'", sClassName.GetString() );
/* That probably took a little while. Let's reset stats. This prevents us /* Give a null update to the new screen. This bumps everything into its
* initial tween state, if any, so we don't show stuff at an incorrect
* position for a frame. */
ret->Update(0);
/* Loading probably took a little while. Let's reset stats. This prevents us
* from displaying an unnaturally low FPS value, and the next FPS value we * from displaying an unnaturally low FPS value, and the next FPS value we
* display will be accurate, which makes skips in the initial tween-ins more * display will be accurate, which makes skips in the initial tween-ins more
* apparent. */ * apparent. */