Dolphin 5.0| Massive game slowdowns/frame drops for no reason

08-26-2017, 12:02 AM #1

A couple of days ago, when I first installed Dolphin, I was able to play the game I play most; Soul Calibur 2. The first day I had Dolphin installed, the game ran perfect. No slowdowns at all (other than the battle with Inferno at least.) But when I started up my computer the next day, I noticed very quickly that even after letting it go through it's routine of opening programs and waking up in a way, Dolphin was causing problems. The most I could get out of that game anymore was a maximum of 50-40 frames in fights or even the character selection. In the menu and start screen though, I got 60 frames. I know it's not my hardware because the game ran fine before, suggesting to me that it's a problem with the program and not my end. Who knows though, I could be wrong. As for my options, I kept them default except for changing the audio to OpenAL and for configuring my controller (Xbox 360 wired, Afterglow type).

In case my hardware info isn't public, I'll post my specs in this thread.

CPU: AMD Athlon II X2 220 Dual Core 2.80GHz (64-bit)
Graphics: NVIDIA GeForce GT 610 (running driver version 384.94, will be updating to 385.41 to see if it makes any difference) (No OC)
Dolphin Version: Dolphin 5.0 (64-bit)
Windows Version: Windows 10 Pro (64-bit)

I've gone and attached screenshots of the framerate drop. I should mention I normally play in fullscreen, but I had to switch to windowed mode to get the screenshots.

I also tried saving the images as a JPEG, but I got a complaint that the file sizes were too large (1MB each) so I had to convert them to GIF :/

**Helios** · 08-26-2017, 12:34 AM #2

Your system was probably BARELY running that game at full speed and then something else in your system changed, stealing processor time and causing this.

You'll need to investigate that and resolve that.

08-26-2017, 12:47 AM #3

(08-26-2017, 12:34 AM)Helios Wrote: Your system was probably BARELY running that game at full speed and then something else in your system changed, stealing processor time and causing this.

You'll need to investigate that and resolve that.

Ah. I didn't even think of that possibility. After closing some programs, it's running fine now. Thanks.