Melty Blood running 60% speed (not a typical slowdown) (solved)

[Tgoh]

Well, for some reason, after testing netplay for the first time, my MBAC is now running at approximately 60% speed.

When I say that, I mean, the game is reporting 60fps, and I can MANUALLY change the fps to 120 and it will run faster (read as 1 real second = 2 game seconds) than it should, however at 60 fps, the game is running SLOWER than 1 real second to 1 game second.

Recorded on the character select screen, 10 game seconds is being recorded as 15 real seconds, and its the same in game.

Now, this is an odd issue, because I was playing only today, and it was fine, until I tested netplay.

Have tried reinstalling, virus scan, etc. Also, it seems to be eating about 85% cpu, however, set at 120fps, the game still performs better than it usually does, so I don't think thats the problem.

Any help would be very much appreciated ^^

Edit: Comp specs:
Pentium 4 3.60ghz
1gb ram
256mb geforce 6800

[Kayin]

Maybe it's your connection?

If you're on a router you should check if anyone on it has been downloading any big files. It helps to shut down anything that might be hogging resources.

[Tgoh]

Wish that was the case, but its offline play as well, which is the REALLY puzzling thing.

[noradseven]

whats your OS its a good chance something messed with the prefs of the game and made the way the game outputs run differently.

[puKKa]

What OS are you using? I'd personaly try running it in compability mode for win2k and win98.
Also, do you get a general slowdown on the whole comp when MB is running or just in-game? Any irregularities on computer tempratures? Tried killing everything else except MB when running it and see if there is something taking too much memory or CPU. 1GB mem is a bit little :3

[REAL DAKANYA TALK]

Its been about a month since this was posted.

The real answer is "update your drivers"

[Tgoh]

Sorry for the late reply, but solution was found. Not 2 days after my initial posts, my PSU exploded. I'm assuming that the fluctuations in power were screwing with the cpu frequency timer, so yeah, problem solved now ^^

[Sh1k1]

Well, glad to know you're back up and running.