responses to user input, but that's it) up until you try to reset, shutdown or swap and the likes. CB v10 locks up, PCSX2 "works" (a.k.a.From here on out, I notice that the games that do not work conjure up this notice in the log: (GameDB) Changing EE/FPU roundmode to 0.Again, selecting cheats and take it to the CB v10 prompt to swap the disc (and use the PCSX2 option to swap ISO). Again, starting from zero (restarting PCSX2 itself) - but this time I'm selecting Shin Megami Tensei : Nocturne (NTSC, SLUS_209.11 // 0圎8FCF8EC).An example of a working game would be Grandia 3 (NTSC, SLUS_213.34 // 0x5B657DAD) - The game boots and works.After selecting cheats, I activate the CB v10 prompt to swap the disc (and using the PCSX2 option to swap ISO).Auto-eject has been turned off CB v10 (in-game option), but this does not seem to make a difference.CB v10 tells it's the game Rez to PCSX2 (according to the GameDB). The following steps and/or info I have to reproduce the problem: I've thusfar managed to limit it down to a single moment where it seems to happen. There seems to be an issue where CodeBreaker v10 (hereafter named CB v10) locks up PCSX2 (either 1.4.0 or the latest GIT builds) with certain games. (note: I posted this somewhere else, but as it didn't get attention, I made it it's own topic - I also removed and added some info as opposed to the original post)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |