
Originally Posted by
sokrin
yeah i've compared the md5 checksum with the known working cb version and they matched. since i'm using cb_launch.elf, it automatically boots to free mcboot and the esr disc would be detected. the screen color changes doesn't occur after cb "start game", but when free boot launches the disc. now - having never gotten cb to work ingame, i'm not sure how this is suppose to work.
What you describe is correct behaviour.
When you use the CB 'Start Game' command ESR is not yet active. It is only launched after FMCB has been started and detects that the disc in the tray is an ESR disc. This causes FMCB to launch ESR to deal with the disc booting, and it is only after ESR has been launched this way that it can begin to show the color flashes to indicate various steps in the game launch (and vector bending). This is in fact intended to provide ffgriever with feedback on what the program is doing, in case of bugs/problems. Text messages would have been preferable for debugging, but are impossible in that runtime environment. (Well, they are possible, but only at risk of adding bugs to the launch procedure.)
cb used to have these joker codes listed on their site. when i check their new site however, it no longer lists the joker stuff. how did you config this button combo (i wish to try it).
That was some time ago now, so I honestly don't remember how I found the gamepad read address (disassembly or conversion from found codes). But the address I use might not be directly useful for you anyway, as it is for the UK PAL version (SLES_541.14) sold here in Sweden.
In case you want it anyway, here it is (raw format):
Code:
E0017FFD 0035BA5C if (*((mem16 *) 0x35BA5C) == 0x7FFD) //if gamepad L3+Square pressed
20340360 000F423F *((mem32 *) 0x340360) = 999999; //Munny variable = 999,999
Hmmm. I just made a quick disassembly of both the US and the UK elfs, and it seems that the US gamepad variable should be 0x0035B55C, and the Munny variable appears to be at 0x0033FE60 according to a non-jokered munny code I found, and that also matches the same between-versions offset of 0x500 for that memory range, so the equivalent US code would be:
Code:
E0017FFD 0035B55C if (*((mem16 *) 0x35B55C) == 0x7FFD) //if gamepad L3+Square pressed
2033FE60 000F423F *((mem32 *) 0x33FE60) = 999999; //Munny variable = 999,999
I haven't tested it myself, but it should work, provided a decent master code, such as "902FD330 0C0C42BD" according to that cheat collection I found for US KH2.
all movie sequence works fine.
Here too.
the game freezes (black screen) when you're about to control Roxas (even on a loaded game).
Never here.
it's not just the KH series, it's pretty much freezes for every game i launched CB with (even w/ no cheat selected).
I never get this nowdays, but it does remind me of a problem I did have at one time, which turned out to be due to the master codes used for the cheat sets.
If the master code is of the type Fxxxxxxx then it will not work properly with patched CodeBreaker. Instead you need to use master codes of the type 9xxxxxxx (in raw format of course).
I do the same on a fat v7, a fat v10 and a slim v15 without any problems.
free mc 1.8b is installed in the memcard, codebreaker is installed on a usb device under the folder BOOT.
Neither should cause any problems (it is only on slim consoles that CB has USB problems.)
and the code i'm using are downloaded from cb's day1 site.
I don't bother with those myself for several reasons, one being that I mostly have european games, and another being that I prefer to have full insight into the code when browsing it in CodeBreaker, and cheats from the CB site are usually encrypted or at least obfuscated, making it a lot of work to make any modifications or additions.
Anyway, if your CodeBreaker problem happens equally with original discs as for ESR, then we can obviously rule out both ESR specifics and burned media issues from having any influence here.
Effectively this only leaves two suspect components, which are the CodeBreaker elf itself and the code sets used with it. If you have verified the CodeBreaker elf as you said, then that too should be ruled out leaving us with the code sets as prime suspects, and then the master code problem I mentioned tops the list of probable causes.
Please list some of the master codes here, so others can check them too, and so we can see if they match the problem I described (may require decrypting them first).
Best regards: dlanor