Jump to content

+ T +

Ultra Members
  • Posts

    1,121
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by + T +

  1. Dipswitches are working here with no problems. If you haven't done so already, delete your savegame from the MS dashboard or delete the folder E:\TDATA\FFFF0504 and try again. If you're running from HDD then also delete the files from the cfg and ini folders in your root directory.
  2. Regardless of whether this ROM exists or not. I'm still going to stick with the CRCs listed in JB's DATs. That way at least I know my source is reliable.
  3. I think you must be referring to the note in the DATs that says 'correct V ROMs not yet known'. The ones being used currently are just the original mslug4 V ROMs decrypted and split into 4. So yes the sound works fine in both these sets.
  4. FBA-XXX Pro v1.08a ============== I've just had it confirmed that the decrypted M ROMs added to the v1.08 build were not publicly available dumps. It seems I was misinformed and therefore have released this fixed build which restores these ROMs to their previous CRCs. Apologies for any confusion this mistake may have caused. + T +
  5. The source I got those CRCs from stated that they were all publically available. However, it's now starting to look as though that may not be the case. I'll confirm this for sure today and if necessary will release a fixed build very shortly.
  6. FBA-XXX Pro v1.08 ============= - Updated decrypted M ROMs to most recent versions. - Re-added mslug5 encrypted M ROM. (a fake is now available with the correct CRC. This should suffice until the real one is released) - The following sets have been added: kf10thua kf97plsa kf2k4spl - And the following PD games: Frog Feast Jonas Indiana and the Temple of Ra - Fixed AES mode in nitd/nitdd - Some other minor updates and corrections. - Re-added the ROMlist counter by request and updated default skin to incorporate this. - Fixed some irregularities in the DATs.
  7. The ROMs have changed. You need the new ROMs.
  8. I think it's a bit late in the day to change FBA-XXX Pro's default save directory. It would be a massive headache for people that have existing savegames and such. You can however change the default directory yourself by opening the default.xbe in a hex editor, searching for the values 04 05 FF FF, and changing them to whatever you like. The new save folder will have the same name as these values but in reverse (ffff0504 in the example above). As for the ROM counter. I removed it to cut down clutter because I couldn't see the point of it. But since some people such as yourself obviously use it for something I'll re-add it in the next build. I did take a look at the MAME source as you indicated in your post. But I really have no idea how that code would fit into into FBA's CPS sprite rendering routines. I'm afraid it would need to be FBA code to be of any use.
  9. Yes. Sorry about that. Just a typo. I've re-uploaded the package with this error corrected so please re-download if you downloaded the old one.
  10. FBA-XXX Pro v1.07 ============= - Updated supported bootleg sets based on the latest information. (thanks to Ferchogtx) - The following sets have been added: ms4boot ms5boot kof2k1bl kf2k1pls kf2k1pla kf2k2spr kf2k2plb kf2k3exa - No more corrupted graphics in ms4plus, ms5plus, kf2k2mp, and kf2k2mp2. - Removed unobtainable mslug5 M ROM. (game runs fine without it) - Added encrypted M ROMs to decrypted C sets. (this is correct for these sets since ideally only the C ROMs should be decrypted) Enjoy!
  11. iq has informed me that real bootleg boards do not use SNK encrypted C ROMs. So all bootleg sets should have their own C ROMs. A confirmed list of these was recently posted over at the RS forums so expect some changes to several of the bootleg sets in the next build (as well as some new additions). This also means that the graphics corruption should no longer be an issue since the true bootleg C ROMs do not require the same kind of decryption or S ROM extraction. All being well, the new build should be ready in the next day or so.
  12. Yes, up until v1.05 ms4plus and ms5plus were using decrypted C ROMs. But it's more correct to use encrypted ones because that's how they are on the actual board. I think what I might do once this bug is fixed is add decrypted and fully decrypted sets for any bootlegs that use the parent set's encrypted C ROMs so users that want to play them don't have to put up with the load times and filesizes if they don't want to.
  13. This particular problem is due to the addition of the MAME sets. Some of the bootlegs added to MAME are unlike any of the sets that have been supported by FBA-XXX Pro previously in that they use encrypted C ROMs as well as a seperate S ROM. To be more specific, sets that have encrypted C ROMs usually do not need an S ROM since the text layer data is contained in the C ROMs and is extracted as part of the decryption process. However when you try to load a seperate S ROM as well as decrypting the C ROMs it seems to cause a conflict which is why you get the graphics corruption you see on the screen. So there are two possible solutions. 1) Go back to using decrypted C ROMs for the affected bootleg sets (easy to do) or 2) find a way of decrypting the C ROMs that does not cause conflict with the custom S ROM (no chance without help from iq). Will keep you posted as things progress.
  14. Don't bother. I'm hoping to have a fixed build out soon. However the kf2k3upl problem doesn't look like a driver issue. Thraxen, do you know if it does the same thing in MAME?
  15. That is absolutely right. But if I may expand on that a little for anyone who is interested: Encrypted sets contain all encrypted ROMs (P, C, M, V). They are the most accurate in terms of how the data is on the actual board. However the decryption process often causes long loading times and encrypted C ROMs do not compress well so the sets can have a very large filesize. Encrypted sets also use a decrypted M ROM due to the fact that M ROM decryption routines are not yet support by any emulator. Non-encrypted sets have encrypted graphics and sound (C, M, V) ROMs but decrypted program (P) ROMs. The only non-encrypted sets supported by FBA-XXX Pro are those that exist in MAME which also exist as actual boards. Decrypted sets contain all encrypted ROMs with the exception of the graphics © ROMs and M ROM. These sets are included to allow users to have mostly accurate sets without the long load times and large filesizes of their fully encrypted counterparts. Decrypted sets also contain an S ROM for text layer data. Fully decrypted sets contain all decrypted ROMs (P, C, M, V and an S). Technically these are the least accurate but require no special driver routines to run hence they load much faster. Filesize is comparable to decrypted sets.
  16. Yeah I've always been in two minds about this. On the one hand it would be great to have FBA-XXX Pro support exactly the same sets as MAME since most other PC emus do and it creates a set standard for ROMsets that means any downloaded set will work straight-out-of-the-box on any emulator, Xbox or PC. But on the other hand, the whole point of FBA-XXX Pro has always been to use the most accurate ROM dumps so that collectors (like myself) have a platform on which to actually play the sets they've spent alot of time putting together and getting right. It's such a shame that MAME didn't use a better source of information when putting together its NG sets. But my understanding is that the developers don't really care that much about the system any more due to all the controversy over the 3-year-rule and such.
  17. I've already explained this several times now so please pay attention as this will be the last. The ROMs FBA-XXX Pro uses are the latest and most correct available. MAME and other emulators do not use the latest and most correct ROMs. They are different. That is why the sets you have will not work. If you want to use FBA-XXX Pro you must update your sets by adding the ROMs that the DAT tells you are missing. I hope this answers your question because I really don't see how I can make the point any more clear.
  18. FBA-XXX Pro v1.06 ============= - Added 2 new PD Neo-Geo games by blastar@gmx.net: Codename - Blue Engel NGEM2K - Fixed kf2k3pcb bios ROM size. - Fixed disabling shortcuts on attached controllers. - Some minor name corrections. Enjoy!
  19. Thanks for that, I'll correct it in the next update. I'll look into fixing this. Again, thanks for reporting it.
  20. Read this for information on xbins. http://www.xbox-scene.com/articles/xbins.php
  21. FBA-XXX Pro v1.05 --------------------- - Updated newer Neo-Geo set names to match those in MAME v0.104. (see note below) - Added the following new sets: kf2k2mp kf2k2mp2 samsh5sh samsh5sn kf2k3bla kf2k3pl - Updated supported Universe bios to v2.2. - Fixed kof2002 'How to Play' screen GFX glitch. (by iq_132) - Replaced old NeoPVC decryption code with tidier version. (by iq_132) - Fixed dipswitch settings for all CPS1 games. Defaults now match MAME instead of everything being set to 'off'. (you will need to delete your old FBA-XXX Pro savegame for these changes to take effect) - Fixed bug in which controllers 2,3,and 4 were not saving PPP & KKK button settings. - Fixed Commands View menu bug. - Added sub-folders to main roms/ directory. (just delete if you don't want to use them) NOTE: Although FBA-XXX Pro's newer NG sets have been renamed to match those added to MAME, the required ROMs are not exactly the same. This is because some of the ROM dumps MAME is using in these sets are not the most correct. Enjoy!
  22. Yeah, you're probably right. I'll leave things as they are then. Thanks for the offer but FBA-XXX Pro is as much for my own use as everyone elses so I don't think it would be right for me to accept donations. Do you have any more info on how the mvsc bug was fixed? Or do you know of an older version of FBA/FBA-XXX in which it was not present? I'll look into the the controller issue, thanks for reporting that one. The gamelist is alphabetical so 'Last Blade 2, The..' comes before 'Last Blade, The..' (apparently [space] comes before [comma] in the alphabet ) As I mentioned previously, I don't have an HD set so I can't test this out. Although since you say you're experiencing this on other emus too it sounds like an issue with your setup. Hopefully someone else can help. Just rebuilding the sets from what you have is not enough you need to make sure you have all the ROMs each set requires. If you've done this and all your ROMsets are correct but you still can't get games to work then please be more specific as to what happens when you try to play them (error messages etc.). The next build will use same sets as MAME v0.104. However, as I said before, a few of the ROM files MAME is using are not correct so they will not be exactly the same since Pro will stick with the most accurate ones. In my opinion I think ROM distribution has been discussed enough. That isn't the purpose of this thread.
  23. I don't know the combination off the top of my head. Try checking the Help screens to see if you can find it there. If not I'll find out tomorrow and let you know. For the next build the quick fix would be to set this combo to something you can't press by accident. But I may just remove the function altogether if it's causing problems as I don't see that it's useful enough to spend alot of time trying to fix. This isn't a priority since I don't have an HDTV. Feel free to buy me one. Perhaps I should just make it so that previews/screenshots use the same folder. Would that be better or worse?
  24. The ROMsets supported by FBA-XXX Pro are completely different to those in FBA-XXX. As the documentation says, you will have to use the DATs to find out which ROMs you are missing and update them. The next build will include ROMsets from MAME v0.104 though even these will not be exactly the same since not all of the ROMs in MAME are correct. Crouching Tiger Hidden Dragon is supported (cthd2003) as are several King of Fighters 2003 hacks, I don't know which you mean by KOF 2003 Boss Edition but again, please check the DATs for details. The PCB set of svcchaos does not currently work. This is a known issue. I'll look into the screenshot problem and try to fix it for the next release.
×
×
  • Create New...