General Emulation > General Emulation

Fatal Fury 2 bugs...

(1/1)

NJ7:
Can't hit the opponent after the first match and after the second the time is always up......the time is fixable if ya use the Universe Bios Infinite Time cheat, but the hitting opponent isn't.....anyone know how to fix this driver?

NJ7:
I looked at the MAME source and the drivers were similar, but something has to be wrong with the protection scheme cause it don't work, anyone got the fix?

// Fatal Fury 2

static struct BurnRomInfo fatfury2RomDesc[] = {
   {"047-p1.bin"   , 0x080000, 0xbe40ea92, 0x10}, //  0 68K code
   {"047-p2.bin"   , 0x080000, 0x2a9beac5, 0x10}, //  1

   {"047-s1.bin"   , 0x020000, 0xd7dbbf39,    1}, //  2 Text layer tiles

   {"047-c1.bin"   , 0x200000, 0xf72a939e,    1}, //  3 Sprite data
   {"047-c2.bin"   , 0x200000, 0x05119a0d,    1}, //  4
   {"047-c3.bin"   , 0x200000, 0x01e00738,    1}, //  5
   {"047-c4.bin"   , 0x200000, 0x9fe27432,    1}, //  6

   {"047-m1.bin"   , 0x020000, 0x820b0ba7, 0x10}, //  7 Z80 code

   {"047-v1.bin"   , 0x200000, 0xd9d00784,    2}, //  8 Sound data
   {"047-v2.bin"   , 0x200000, 0x2c9a4b33,    2}, //  9
};

STDROMPICKEXT(fatfury2, fatfury2, neogeo);
STD_ROM_FN(fatfury2);

static int prot_data;

unsigned char __fastcall fatfury2ReadByteProtection(unsigned int sekAddress)
{
   unsigned short res = (prot_data >> 24) & 0xFF;

   switch (sekAddress) {
      case 0x255551:
      case 0x2FFFF1:
      case 0x200001:
      case 0x2FF001:
      case 0x236001:
      case 0x236009:
         return res;

      case 0x236005:
      case 0x23600D:
         return ((res & 0xF0) >> 4) | ((res & 0x0F)

FerchogtX:
I'm not pretty sure but maybe the memory values are wrong for FBA (?)... BTW it looks difficult to fix because is the SAME code as MAME so, it should work properly... but it doesn't.
See ya!!!!! :D

iq_132:

--- Quote from: FerchogtX ---I'm not pretty sure but maybe the memory values are wrong for FBA (?)... BTW it looks difficult to fix because is the SAME code as MAME so, it should work properly... but it doesn't.
See ya!!!!! :D
--- End quote ---

Yeah, I noticed that too.  There's not one difference.  I remember Jan (FBA Dev) saying that the memory reading/writing stuff isn't set up correctly.

Navigation

[0] Message Index