Jump to content

+ T +

Ultra Members
 View Profile  See their activity

  • Posts

    1,121

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Posts posted by + T +

    MAMEoX with 090 CPS2 Support!

    in XBOX Hacks [/xbox]

    Posted

    nice to hear that + T +, i hope you can share your src cuz it would be great to finally play matrim without breakups in the sound.

    The old code is still in the current source, it's just commented out in favour of the new stuff. Then it's just a matter of a few little adjustments here and there. An adept coder like djohng would have no problems re-implementing it.

     

    I'd be happy to post my modified source but my build of FBA-XXX is so heavily customized to my own romsets and tastes that many of the roms from djohng or gogo's version wouldn't even show up. :rolleyes:

    MAMEoX with 090 CPS2 Support!

    in XBOX Hacks [/xbox]

    Posted

    the fba-xxx probs are due to a buggy src tho gogo and co. has done a lot of miracles with it.

    Actually the worst sound problems were caused by changes to the VMM routines that were made in later versions of FBA-XXX. I was able to virtually eliminate all sound issues by restoring the original VMM code. :P

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted

    I understand what you're saying but I think we should keep in mind that the purpose of MAMEoX is simply the playing of arcade games on the Xbox whereas the purpose of MAME is to emulate arcade hardware as accurately as possible no-matter the performance cost to low-spec systems. There may come a time at some point in the future when just blindly updating to the latest core will actually cause MAMEoX to slip to the point where the Xbox struggles to run anything at all at a decent speed. Then the only way forward for the project will be backwards as developers begin to look at which drivers were the most Xbox friendly. The ultimate goal being, not just an Xbox version of MAME, but an 'Xbox optimized' version of MAME.

     

    Just my thoughts. :shootem:

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted

    The VMM issue is seperate to the mslug4nd problem. In fact I got so sick of the sound glitching every so often in big games when using any compile based on 09-01-2004 that I'm now using the 06-04-2004 release and just adding the features/drivers that I want to it. samsh5sp works just as nicely on this version as do all the most up-to-date rom dumps that I have. The only difference I've found is that to get the transparencies from 512Kb S roms in games like SvC Chaos, the rom data has to be in memory order whereas 09-01 required it to be in rom order, that's it so far as I can tell. IMO this version is a far better base to work on.

     

    Manto should never have changed the VMM code in the 08-02 release. It was much better as it was.

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted

    Bad sound (that is to say slightly crackly at times) in the larger games is something that got noticeably worse when the VMM routines were changed in the 08-02-2004 release. If you try the 06-04-2004 version you'll hear that it still occurs only to a lesser degree. A good place to check this is in SvC Chaos on the character select screen. Notice how when you move the selector to each character the 'bleep' that sounds is broken up and crackly, however if you move it back over a character you've already highlighted then it sounds fine.

     

    I did try to re-implement the original VMM routines into my own build which I'm continuing work on but I think it would take a level of coding skill that I'm not yet capable of. Perhaps djohng might consider giving it a go. But I really don't know why Manto changed the VM routines in the first place, there was nothing wrong with them as they were. >_

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted

    I wonder if someone here might be able to help me out. I'm trying to get hold of sources to versions of FBA-XXX prior to the 08-02 release to test a theory. There is an old GOGO source on xbins but I haven't a clue which version of the emu it's from.

     

    So if anyone has any old sources lying around could they please let me know? Many thanks. :D

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted · Edited by + T +

    The build I've released patches for uses much older S roms that are mostly incomplete 128Kb versions. I used these in the build because they're the ones that came with the original releases of the romsets and so people are far more likely to already have them than the new ones.

     

    The custom build I'm using on my Xbox has been updated to include all the latest drivers for the most recent (and in many cases final) dumps of the roms including the above S roms. I was going to release patches for this build in case anyone else was interested but djohng's upcoming version sounds far better than anything I can produce so, if he doesn't mind, I think I'll leave the releasing side of things to him from now on. :D

     

    The following is a list of updated roms in my unreleased custom build (all tested and working):

    garoud.zip

    ----------

    motwn_s1.rom 512Kb be2ba1a5

     

     

    ganryud.zip

    -----------

    gann_s1.rom 128Kb a8dadec9

     

     

    preisl2d.zip

    ------------

    pi2n_s1.rom 128Kb 666cabdc

     

     

    s1945pn.zip

    -----------

    s45pn_s1.rom 128Kb 121a4f94

     

     

    nitdd.zip

    ---------

    260-p1.bin 512Kb bdef9b73

    260-s1.bin 128Kb dd3bf47c

     

     

    sengok3d.zip

    ------------

    261-p1 2.0Mb 6fc85b45

    sen3_s1.rom 128Kb c1e27cc7

     

     

    zupapad.zip

    -----------

    zupan_s1.rom 128Kb 307967ba

     

     

    mslug3nd.zip

    ------------

    256-ph1.rom 1.0Mb c871c036

    ms3n_s1.rom 512Kb 2628d663

     

     

    mslug4nd.zip

    ------------

    263-p1.bin 1.0Mb 249c1411

    263-s1.bin 512Kb c349ad60

    263-v1d.bin 8.0Mb fd6b982e (join old v1d + v2d)

    263-v2d.bin 8.0Mb 20125227 (join old v3d + v4d)

     

     

    mslug5nd.zip

    ------------

    268-s1.bin 128Kb 64952683

    268-m1d.bin 256Kb 792e07c1

     

     

    kof2knd.zip

    -----------

    257-p1n.bin 1.0Mb f2eca98f

    kof2k_s1.rom 512Kb 38901d4d

     

     

    kof2001d.zip

    ------------

    262-m1a.bin 128K 56a9067f

    kf2k1_s1.rom 128K 8c5c479e

     

     

    kof2002d.zip

    ------------

    265-p1.bin 1.0Mb f5bea3a9

    265-s1.bin 128Kb e0eaaba3

    265-c2d.bin 8.0Mb f09b84a9

    265-v1d.bin 8.0Mb 0fc9a58d (join old v1d + v2d)

    265-v2d.bin 8.0Mb b8c475a4 (join old v3d + v4d)

     

     

    kof2k3ba.zip

    ------------

    271b-s1.bin 512Kb 3b658d26

     

     

    matrimnd.zip

    ------------

    266-p1.bin 1.0Mb 7be60e6b

    266-s1.bin 128Kb aff2a3be

    266-m1d.bin 128Kb 7bcafd98

     

     

    svc.zip

    -------

    269-s1.bin 512Kb AD184232

    269-m1d.bin 128Kb fd4f0ff9

     

     

    svcplus.zip

    -----------

    269p-p1.bin 6.0Mb 397E7F8E

    269p-s1.bin 512Kb 06125f98

    269-m1d.bin 128Kb fd4f0ff9

     

     

    samsh5nd.zip

    ------------

    270-s1.bin 128Kb 2ad6048b

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted · Edited by + T +

    The S rom contains the text layer for the game. This data usually resides within the encrypted C roms and is extracted as part of the decryption process. However since using pre-decrypted roms (nd sets) bypasses this time-consuming process, a pre-extracted S rom is usually necessary.

     

    FBA-XXX, on the other hand, is designed to extract S rom data from even pre-decrypted C roms unless otherwise specified in the driver. This makes the loading of nd sets take longer than they should and also is annoying because (and call me old-fashioned if you like) a true pre-decrypted set should always include an S rom. So I'm glad to hear that support for them is being re-included in djohng's promising sounding build.

     

    And none of the above roms are overdumps. Those are all perfectly correct CRCs as extracted from the original C roms. The only exception is kof2003 which actually has 1Mb worth of S rom data in its Cs. But the 512Kb works much better with the current set. The names are just what they are called in my sets ATM, ultimately the names of all roms need to match those in the individual driver.

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted

    Yep, sure did with the S rom.

     

    Then here's the driver (note that I've removed the s rom decryption lines at the bottom since with the s rom added they are unnecessary):

    // Samurai Shodown V (Decrypted C & V)

     

    static struct BurnRomInfo samsh5ndRomDesc[] = {

    {"270-p1.bin",  0x400000, 0x0379698b, 0x10}, //  0 68K code

    {"270-p2.bin",  0x400000, 0x91979dee, 0x10}, //  1

     

    {"270-s1.bin", 0x020000, 0x2ad6048b,    1}, //  2 Text data

     

    {"ss5_c1.rom",  0x800000, 0x726abb40,    1}, //  3 Sprite data

    {"ss5_c2.rom",  0x800000, 0x76806188,    1}, //  4

    {"ss5_c3.rom",  0x800000, 0x82db9dae,    1}, //  5

    {"ss5_c4.rom",  0x800000, 0xf8041153,    1}, //  6

    {"ss5_c5.rom",  0x800000, 0x2219186a,    1}, //  7

    {"ss5_c6.rom",  0x800000, 0xd225120d,    1}, //  8

    {"ss5_c7.rom",  0x800000, 0xd245d493,    1}, //  9

    {"ss5_c8.rom",  0x800000, 0xeb06c9cc,    1}, //  10

     

    {"270-m1d.bin", 0x020000, 0x18114fb1, 0x10}, // 11 Z80 code

     

    {"270-v1d.bin", 0x800000, 0xe5c71699,    2}, // 12 Sound data

    {"270-v2d.bin", 0x800000, 0x70b7083d,    2}, // 13

    };

     

    STDROMPICKEXT(samsh5nd, samsh5nd, neogeo);

    STD_ROM_FN(samsh5nd);

     

    struct BurnDriver BurnDrvsamsh5nd = {

    {"samsh5nd", "Samurai Shodown V (decrypted C & V)", "Decrypted C-ROMs", "SNK Playmore / Yuki Enterprise", "Neo Geo", "2003", "samsho5", "neogeo"},

    BDF_GAME_WORKING | BDF_CLONE, 2, HARDWARE_SNK_NEOGEO | HARDWARE_SNK_SWAPC,

    NULL, samsh5ndRomInfo, samsh5ndRomName, neogeoInputInfo, neogeoDIPInfo,

    NeoInit, NeoExit, NeoFrame, NeoRender, NeoScan, &NeoRecalcPalette,

    nNeoScreenWidth, 224, 4, 3

    };

     

    how come when I applied ur first patch,+T+, on the mame.xbe file.. the emu didnt load,, for that matter didnt show up on my emu list, i tryed patch on regular default, saw it on my list.. but didnt load.. the xbox frooze

     

    Have you tried the latest patch?

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted · Edited by + T +

    Yes, I included the s-roms in the build. It's better on my nerves, since each change requires a compile.

     

    Are you using the 512Kb s roms for the romsets those that support them?

     

    Here are the 100% correct crcs if they're of any use to you :P :

     

    garoud.zip

    ----------

    motwn_s1.rom 512Kb be2ba1a5

     

    mslug3nd.zip

    ------------

    ms3n_s1.rom 512Kb 2628d663

     

    mslug4nd.zip

    ------------

    263-s1.bin 512Kb c349ad60

     

    kof2knd.zip

    -----------

    kof2k_s1.rom 512Kb 38901d4d

     

    kof2k3ba.zip

    ------------

    271b-s1.bin 512Kb 3b658d26

     

    svc.zip

    -------

    269-s1.bin 512Kb AD184232

     

    svcplus.zip

    -----------

    269p-s1.bin 512Kb 06125f98

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted · Edited by + T +

    All:

     

    I'm working on a version of FBAXXX that doesn't have any of the issues listed here.  Everytime I see someone mention an issue, I've checked my version and I don't have it.

     

    Metal Slug 4 works without locking. and Samurai Showdown 5 both versions run great.  Metal Slug 3, 4 & 5 do not have graphics issues, with the exception of the "warning" screen" being garbled on MS4 encrypted, but I think that's a bad rom dump...the rest of the text is fine.  MS4nd doesn't have a garbled warning screen...so I'll probably reencrypt this rom to see if I have the same problem.

     

    I've also added all of the debug drivers and homebrew neogeo roms...just for kicks.

     

    And the newest 2 sets for SS5 Special...had them working last night without any issues...other than the V & M roms not being available...

     

    -djohng

    Phew! Finally someone who knows what they're doing. I guess I can take a rest. :P

     

    I just have one question. Since it isn't against the rules, would it be possible for you to put up the modified source-code for d/l? I'd love to take a look to compare and see exactly where I've been going wrong. This has been a great learning experience for me. ;)

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted · Edited by + T +

    Well I've replaced the samsho5 driver with a more recent one in the hope that this might help (again I don't have the encrypted set myself). However this driver was written for a newer version of the romset and I've simply substituted the CRCs for the current FBA-XXX set so who knows.

     

    Unfortunately I'm not a coder, so things like this are the best I can do when problems arise. If anyone with more knowledge can help out then I'd very much appreciate it. :P

     

    http://www.thraxen.com/emu1/FBA-XXX_09-01_newsets_FIX3a.zip

    FBA-XXX compile help

    in Final Burn (FBA/FBL/FBC)

    Posted

    Prican, I've had another crack at adding IQ_132's code. There were some duplicate lines last time. See if it works now:

     

    http://www.thraxen.com/emu1/FBA-XXX_09-01_newsets_FIX2.zip

     

    As for matrimnd, does anyone have the v2d and v4d roms from the original dump?:

     

    266-v2d 945F8831

    266-v4d 393C9A62

     

    If so perhaps substituting these for the newer ones in the driver might help the sound problem. I don't have them to hand ATM so I'd be grateful if someone could just put them in their matrimnd.zip and give it a try (just make sure CRC check is off).

     

    +T+

     

    I have a bug to report.

     

    When the banned roms were pulled from the FBA-XXX source by manto the loading text bug also seemed to go away since the 31/08 version.

     

    The loading bug text for example in version 02/08 was:

     

    Found D:\roms\kof98.zip okay

    Found D:\roms\kof98.zip okay

    Found D:\roms\kof98.zip okay

    Found D:\roms\kof98.zip okay

    Found D:\roms\neogeo.zip okay

    Found D:\roms\neogeo.zip okay

    Found D:\roms\neogeo.zip okay

    Found D:\roms\neogeo.zip okay

     

    It should just be:

     

    Found D:\roms\kof98.zip okay

    Found D:\roms\neogeo.zip okay

     

    I just tried the 01/09 version with your IPS patch and this bug is back so my suspicion is that its related to the NeoGeo drivers because I did a clean install of your version and the text bug is still present.

     

    Can you look into this?

    I had to use several files from the 08-02 version to make this build work properly. So it's not surprising that some previously fixed bugs might return. If anyone can give me an idea of how I might go about addressing this then I'll happily take a look. But surely it's not that big a problem is it? :P

×
×
  • Create New...