Currently, the value the game is looking for past 20466D is FFB7, it looks for this value in (aligned) memory, but it exists no where in memory so it just loops forever.īut, I don't see any relevent commits in gensplusgx that would fix this, at least not in the cpu core itself, it seems to be doing everything identically to what we have. The problem is that the checker afterwards has no such bound in place, it keeps checking and only expects to stop at 2046B5. Where things go wrong is that during the time it is loading data, it checks if the data it is pointing at is FF, then stops:Ġ4628C: 0C10 cmpi.b #$FF, (A0). So the game uses this opcode to load a bunch of data into RAM (starting at EBB6), from ROM (starting at 204575) then it checks some stuff using that data. Part of the problem in recognizing what's happening is that BizHawk incorrectly disassembles the opcode 0108 to BTST instead of MOVEP, even though it's being executed correctly. The game is doing some kind of check by transferring word sized data from unaligned memory. Okay some info on this one (at least for Madden NFL 98)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |