Not urgent, nor game-breaking, but would be nice to have fixed before next stable release.įrame limiting and Frame skipping disabled V1.5.-g41bfb6e80, but also happens on stable 1.4.0 and earlier. This has been happening ever since I started using PCSX2, but I'm currently using build v1.5.-g41bfb6e80. It's just a form of lag, but I'm running a GTX 1080 and not really pushing the internal resolution that far, so I wouldn't tend to expect performance like that, even with how resource-intensive PCSX2 can be at times.
After the pause, the emulation speed immediately returns to 100%. It happens whenever the sun comes into and out of view. Sound cuts out and the image freezes and then resumes. This is what I found I changed the VU0 setting to "Interpreter" and suddenly performance was perfectly smooth, even when I ramped up all of the graphics settings to near their max and switched to 4x native resolution.When I drive on sunset and/or night tracks, emulation will pause for a split second when taking certain corners. So there's a chance that a single counterintuitive setting will make a 500% difference in performance.
Pcsx2 slow motion Pc#
If you have a modern gaming PC that is struggling with 12-year-old PS2 games, you likely have plenty computing power, it just isn't being allocated correctly.This is a handy approximation of how well the game is performing, and in my experience so far, audio performance problems are usually connected to video / general emulation performance problems, not isolated.
Pcsx2 slow motion windows#
This will be obvious to most people who have spent more than a few minutes tinkering with PCSX2's settings, but on Windows you can see the framerate displayed in the title bar of the game window.My experience is mostly summed up by Mazura - you keep trying one thing at a time until you see improvements - but I have 2 things to add to that: Increasing performance in an emulator is complete trail and error an experiment that requires an unassailable control group (the one thing rule) and a whole lotta patience. It's the only way to be sure that everything you've done has increased performance rather then being a detriment and that whatever you've changed has actually taken effect. Loading time is the killer, because when I say one at a time, I mean (it!) close PCSX2, re-open it, and change ONE thing and then boot the game again and load a save. For reference (ignoring my old HDD score of 5.7) my Windows Experience Index average is 6.9 and my processor name doesn't start with an i. IIRC, it took me 10+ hours to get FFXII running acceptably. While it's unlikely that your GPU is the bottle neck, being that it's an emulator, absolutely everything has to go through the CPU).Ĭontinue repeating both of the above with different plugins until it works well enough that it's playable (unless you've an i7 processor, sometimes playable is as good as it's ever going to get). Repeat this with the video settings (the audio will stutter if the CPU gets bogged down. Try every audio option ONE AT A TIME and note performance ( do not ignore the 'one at a time' rule). If you're complaining about only getting 35+ fps. I'd tell you to look here, except that none of those answers go into just how much work it is to get an emulator running smoothly (on less than stellar hardware.
0 kommentar(er)
