+ T +

A good start would be to look at the DATs. Any set that as a note stating "uses xxx ROMs for now" is having to use substitute ROMs because there is some problem running the correct ones. These issues all need fixing eventually. And some sets marked as NOT_WORKING are down to emu issues also (like kof2003d and svcchaos). Not to mention the fact that some sets are having to use incorrect ROMs because the correct ones are not yet publically available. Basically there's a whole lot to do and I'm sure still more issues are waiting to be discovered. So there's really no point in trying to list it all. I have no plans as to when or even if some these issues will be addressed, I prefer to just take things as they come.

I appreciate the encouragement. But as I said before, there will never be a 1.0 build. There will always be more to add/fix/improve. FBA-XXX Pro will always be a work-in-progress. And that's the way I like it.

djohng is currently taking a look at the NeoSpriteROM issue. If it can be fixed then it should mean that the new C descrambling code for svcboot/cthd2003 will work. This should fix the problem with cthd2k3a. With kf2k2pls, I changed the C ROMs but it's still using kof2002bInit (oops). Will sort out for next time.

If you can provide me with the info on this set then I'll add it to the next update.

That's interesting. And a big thanks to you both. Maybe Manto will be nice enough to share the secrets of his speed boost next.

Just to say that I've updated the patch to work with fbaxxx_26_04. I'll see about adding Manto's Psikyo sound fix when I do the next proper update.

UPDATE: - Fixed sngok3d as clone of sengoku3. - kf2k2pls/kf2k2pla now work using decrypted C ROMs. - Added new controller config method. (by GogoAckman) - Added s1945 and tengai fix. (by GogoAckman) - Updated package files and ReadMe.txt. (and first post in this topic) Once again, MASSIVE thanks to Gogo for sharing those fixes. Both he and Manto were correct, I never would have figured it out on my own. Hope I can return the favour some time.

It doesn't work. People just go for the "new" version every time regardless of which ROMs they have.

I know what you mean about X-S. I won't register there because all they seem to do is cause trouble for people who don't agree with their way of thinking. The reason why I've not wanted to release the NG drivers is because I always assumed that if I did then FBA-XXX would use the updated ones instead of the ones it currently does. I think this would be a shame because FBA-XXX's ROMsets are the ones that are most widely available on the net and therefore are the ones that most players will have. So, by having two seperate versions, everyone can enjoy the games and be happy whether they care about having latest ROMs or not. Also, since I'm not much of a coder, Many of the changed parts of the source (particularly the NG drivers) are a mess and really need some cleaning up. I keep meaning to try and do it but never seem to have the time. I'm very glad to hear you say that FBA-XXX is still open-source. The code has always been an excellent source of learning for me. And I'm certainly looking forward to finding out the cause of the s1945 problem. Many thanks, and please let me know if I can ever be of any help to you. + T +

So if I release the source minus the NG drivers would you consider making FBA-XXX open-source again? Nobody's fighting or squabbling. Just discussing. Please don't confuse what you see here with what you see on other forums.

I think djohng may have an idea of what's up with tengai/s1945. But he's been having some computer problems lately. Gogo, just like with slammast and s1945p I'm happy to share any part of Pro's source with you. The only part of the source that I don't want to release yet is the NG driver files. And I don't think you'd want to use those anyway because then your users would complain that the ROMs are too hard to find. That's why I think it's good to have two versions.

Yes, I've seen that in that instance 'ReadUBYTEFromROM' is used. But this requires arguments, so it can't be used as a replacement when you have a line like this: unsigned char *rom = NeoSpriteROM; Thanks for replying Gogo. Any more help you can offer would be very much appreciated.

You're right about Sengoku 3. The clone set wasn't assigned correctly. This will be fixed in the next update. As I suspected, the problem with kf2k2pls and kf2k2pla is the 'NeoSpriteROM' entry in the C descrambling code. I have no idea how to fix this so unless someone else can help those sets are just going to have to use decrypted C ROMs for the time being.

Well those sets are all supported (except 'kof2k3plus' that sounds like a ROM-hack, Pro does not support these). Try deleting any previous FBA save data. Either delete the savegame from the dashboard or delete the folder E:\TDATA\ffff0504.

These are the Bios sets: acpsx ar_bios atpsx atluspsx konamigv decocass crysbios cvs hng64 maxaflex megaplay megatech macsbios neogeo nss pgm playch10 psarc95 stvbios skns konamigx taitofx1 taitogn tps cpzn1 cpzn2

I think I know the problem with kof2k2pls. It's the same issue as with samsh5bl and the new svcboot C descrambling code. All these routines use the NeoSpriteROM variable. And while this works fine in FBA PC, the Xbox version does not use this at all and I haven't been able to figure out what it should be replaced with. If I could solve this problem then my to-do list would be alot shorter. Nonetheless I will take a look at this one and see what I can figure out. If the worst comes to the worst I can always get kof2k2pls working by temporarily using kof2002d's C ROMs instead of the bootleg ones.

Thanks for the info Gogo. Perhaps it's down to Manto's improved memory handling then. Which core was FBA-XXX using before the option was added?

I think the problem is that Manto (BDiamond) doesn't want anything to do with FBA builds that violate the 3-year-rule. I believe this is the reason he chose not to release the sourcecode to his build and I respect that. But in addition to the tengai/s1945 fix, I'd also be interested to know what the exactly the 'M68000 Emulation' option does in his build. It has two options; Fast and Accurate, and when set to Fast it really gives a big performance boost. At first I thought it was just enabling the SPEEDHACKS in the code as I did to fix the performance issues s1945p. But when I enable all the SPEEDHACKS I get alot of sound break-up in CPS2 games for some reason, so I guess that's not it. IQ, you know the FBA code well, do you have any idea what this Fast/Accurate switch might be?

UPDATE: - Added improved kof10th driver. (by BDiamond) - Fixed kof2k3up text layer. - Fixed no sound problem in bbakraid.

I must've used the wrong NeoTextROMFixType code. Sorry. I'll fix it for the next update.

Battle Bakraid already works perfectly with full sound. Try going into the save directory (E:\TDATA\ffff0504) and deleting the game's config files. Then run it again.

Nope. If it did, you can be sure I'd mention it in the update list.

Some things that need fixing in Pro: - svcchaos rom size problem. - kof2003 P ROM decryption code. - svcboot and samsh5bl C ROM descrambling code. - tengai/s1945 psikyo drivers. - BDiamond driver for kof10th. (will be in next update) - Any other sets that are noted as using substitute ROMs in the DATS. Most of these issues are beyond my current level of coding skill. So unless somebody with more knowledge is willing to help, I don't foresee them being solved any time soon. I think perhaps we are approaching the stage where FBA-XXX Pro has come as far as I can take it.

The only ROMs that have changed in FBA-XXX Pro since the last MAMEdOX patch are bootleg/hacked sets and these weren't included in the update. So the current patch is still up-to-date.

UPDATE: - Fixed black screen bug in rastan. (thanks to TMaul) - Fixed inputs in jockeygp and other gambling games.