From 266875132d6f199ba1ac188b21b4951040cdf818 Mon Sep 17 00:00:00 2001 From: ramapcsx2 Date: Sat, 22 Nov 2008 20:54:55 +0000 Subject: [PATCH] Fix for custom frame limit crashing pcsx2 on startup. Thanks to tmkkmac for spotting it ;) git-svn-id: http://pcsx2-playground.googlecode.com/svn/trunk@358 a6443dda-0b58-4228-96e9-037be469359c --- pcsx2/Counters.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pcsx2/Counters.c b/pcsx2/Counters.c index 788d7e270f..0cebba4bf6 100644 --- a/pcsx2/Counters.c +++ b/pcsx2/Counters.c @@ -227,7 +227,7 @@ static __forceinline void vSyncInfoCalc( vSyncTimingInfo* info, u32 framesPerSec void UpdateVSyncRate() { - const char *limiterMsg = "Framelimiter rate updated (UpdateVSyncRate): %s fps\n"; + const char *limiterMsg = "Framelimiter rate updated (UpdateVSyncRate): %.2f fps\n"; // fixme - According to some docs, progressive-scan modes actually refresh slower than // interlaced modes. But I can't fathom how, since the refresh rate is a function of @@ -263,7 +263,7 @@ void UpdateVSyncRate() if( iTicks != ticks ) { iTicks = ticks; - SysPrintf( limiterMsg, Config.CustomFps ); + SysPrintf( limiterMsg, (float)Config.CustomFps ); } } else @@ -272,7 +272,7 @@ void UpdateVSyncRate() if( iTicks != ticks ) { iTicks = ticks; - SysPrintf( limiterMsg, (Config.PsxType & 1) ? "50" : "59.94" ); + SysPrintf( limiterMsg, (Config.PsxType & 1) ? 50.00 : 59.94 ); } }