You can tell before the map-getting whether or not the game will freeze at the map spot (or any other similar sound effect) since there will be a loud buzzing sound when you are at the game-file select screen. I can indeed help talk you through the best settings for PCSX2 for this game. There was one in the past, back when the SVN update fixed this, but it has long since died. Maybe I will also make a new thread about this on the PCSX2 forums. Since save states are dependent on the emulator version, I might have to keep doing that everytime a new emulator version is released. That way, we could provide it to PCSX2 users who want to circumvent the buzzing / freezing glitch. Hmmm, maybe I should make a save state that gets you past the buzzing, but occurs before the game even begins. It hurts the ability for people to access this amazing game and fantastic translation. Having emulation issues can be offputting to many people, especially those not familiar with the emulator already. Not many people have a modded PS2, or a memor32 or a FreeMCBoot to make this work on their console. People have reported having good luck getting past the buzzing sound by spamming the tab key while the game loads (this changes the frame limiting and apparently helps somehow. This will get you past the part where you have a chance of your sound thread dying. That way, when you turn on the emulator, you can immediately load your save state when the intro screen comes on. process every time you start the emulator up, I recommend using save states in the game as well as saving at the Church (just to keep your memory card on track with your progress). To avoid having to do this load - reload - reload. Once you have gotten the game to give you the intermezzo music, you are set. You should hear the usual Intermezzo music instead. I can say this: the issue occurs at random, and you can work around it by continuing to load the game over and over again until you don't get the buzzing sound at the game select screen. I don't remember which SVN revision fixed this issue, so I can't test it without doing some deep digging. Is it possible to take the plugin from one of the working versions and use it to replace the one that comes with 1.0.0? (1.0.0 is what I'm using and it's broken.)
0 kommentar(er)
