Nice. Funny that emulators would have the exact same bugs. Is that due to shared code, or maybe certain things the game does that tend to fail the same way even if the source issue is different?
Usually we have our own video code for things (well, iq_132 writes it), but taito f3 is a very complex beast, so we're using the video code from MAME. It's funny because even Taito Legends for ps2/xbox have these same bugs
Before we ported the F3 driver, I'd never played any F3 game before. Seeing these great games in such a sad state was heartbreaking, really. Especially after putting weeks into perfecting the driver for FBAlpha. Due to the complexity of the F3 video code, it's no wonder that it's been broken for so long, nobody wanted to take the time to figure out how it worked and try to fix it. There are 3 other video bugs left, and I plan to focus on them for the time being. Luckily, some of the fixes I make made it back into MAME. Maybe these will
The same exact thing happened with Beast Busters / Mechanized Attack - iq_132 did a driver for these, and having never played the games before, I quickly fell in love with them (Beast Busters especially), but when I finally made it to the end of the game, the ending scene was all broken. (also a few things in Mechanized attack, like the Helicopter in stage 2 or 3) This time we didn't use any code from MAME, but the bug existed in both emulators because it was simply not known how the yscroll+wrapping worked. Since it was the last games SNK made before Neogeo, a hint on how to fix it was in the Neogeo video code, but it still took a week or 2 of trying things before I got it. In the end, just like the arabianm fix above, it only required changing 2 lines of code.
best regards,
- dink
