Emulator Issues #8125
Project Zero 2: Extreme Slowdowns
Project Zero 2
What's the problem? Describe what went wrong in few words.
What did you expect to happen instead?
It to at least be somewhat playable.
What steps will reproduce the problem?
1. Start the game.
2. After the very first cutscene, when you first arrive in the village and are able to move around, you will be moving extremely slowly - audio will crackle, and your character's movements will almost slideshow-level.
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Not that I know of.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Is there any other relevant information? (e.g. logs, screenshots,
Config does not seem to effect it. I've lowered all my graphics settings to the lowest, nothing happens. It's SLIGHTLY better on lowest resolution, but still unplayable.
If I had to guess the cause...maybe it's the film-grain/blur filter that the game uses?
#6 Updated by redherochildboss about 7 years ago
Hold on, I might have found the cause.
For whatever reason, this game must be super sensitive to anti-aliasing.
When I tried it on lowest settings, I didn't have AA turned fully off, just to 2x. With anti-aliasing completely off, it's playable, if still a little slow.
#9 Updated by JMC4789 about 7 years ago
Your GPU could be outright maxed out; which is weird.
Anyway, Dolphin doesn't normally take performance issues unless -
You can narrow down a performance regression from a merge
It's an extreme, unusual performance drop (aka, dropping to single digits for a certain moment/effect)
Other exceptions I can't think of right now.
#10 Updated by redherochildboss about 7 years ago
What would cause that? It's never happened in any other game.
Are there any logs that might help?
Alright, it's not that severe. Basically what it is is that if a ghost Blooms during a fight, the purple glowy effect causes minor fps drops and noticeable audio stutter, but it's still very much playable, so I doubt it deserves its own issue.
#12 Updated by rigation about 7 years ago
This game is very demanding because it has copy to RAM set in game.ini, anyway with an old e8400 and a gtx650ti, where you say there should be a slide show, I get around 27 fps - 90% speed using Direct3d (wich for me is as usual better than OpenGL in copy to RAM).
If you wanna play it smoother set EFBToTextureEnable = True in game properties/edit config (but captured photographs in the album will be black), this almost doubles the above fps/speed for me.
#15 Updated by pauldacheez about 7 years ago
The "wrong size" warnings are normal for most games (someone should fix those, they're useless), but the "Unknown BP opcode" warnings might be a little more serious.
46:45:111 BPStructs.cpp:681 W[Video]: Unknown BP opcode: address = 0x00000069 value = 0x000004ed
46:45:111 BPStructs.cpp:681 W[Video]: Unknown BP opcode: address = 0x00000046 value = 0x00000273
For all I know they could be just as harmless as the rest of the log, but let's throw it at our FIFO veteran just to be sure.
#17 Updated by rigation about 7 years ago
No, for example 4.0-3694 is a bit slower than 4.0-5168 with this game (besides I don't think that FF2 uses BB).
If you think that x86 version - 1609 was perfectly playable maybe it is because you played it using copy to textures, in fact that revision was much slower (I got 30 fps in places where now I get 50...)
#21 Updated by redherochildboss about 7 years ago
OK, well, in my personal experience, the issue is 100% Anti aliasing. I've tried it with EFB to texture and EFB to RAM, the performance issues are extremely negligible. On the other hand, going from no AA to 2x AA makes it unplayable.
So, I'm fully convinced it's antialiasing and has next to nothing to do with EFB to RAM.
(Also, any leads on those Unknown Opcode errors?)