spycat

Hi @DerHof2007 Once you've deleted your games from LaunchBox , select Tools, Clean Up Images to remove all images for the deleted games.

Hi @ResidentEvul13 The Project64 error may be due to the Don't Use Quotes (primarily for Project64 1.6 and lower) setting in the Edit Emulator window. For Project64 to auto-launch games this tickbox must be enabled.

It works with MAME (MESS) but I never tried a controller with it. The standalone emulator o2em118win also works, and I tested this successfully before with my old PS2 controller. There's an old thread about this somewhere on the forums.

Yes, with Mame 182, doa2m has become the parent, and doa2 is now a clone. The other clone doa2a is unaffected. In a nutshell doa2.zip has been renamed as doa2m.zip and vice-versa, with the following changes. The file doa2verm.ic22 has moved from the old doa2m clone to the new doa2m parent. And the file epr-22207.ic22 has moved from the old doa2 parent to the new doa2 clone. Out of curiosity, I tried this out manually, using 181 version roms, and they both now pass an audit with Mame 182.

Hi @SvekkeRAFC I've just noticed that the screenshot of your MAME roms folder has 2 CHD files. Ideally, CHD files should be put in subfolders within the roms folder named after the games that use them. So kinst.chd should be moved into a folder named kinst And cap-33s-2.chd should be moved into a folder called sfiii3

Hi @SvekkeRAFC I don't think that your issues are CHD related, as, while Killer Instinct and Street Fighter III 3rd Strike both use a CHD, Ultimate Mortal Kombat 3 and Sunset Riders do not. The screenshot audit of Ultimate Mortal Kombat 3 (when run via LaunchBox) you posted seems to indicate that all or nearly all of the files of umk3.zip needed by MAME for this game are either not found or incorrect. As this game works for you when run directly from MAME, but not via LaunchBox. it might be worthwhile to compare the location of this game that Mame is using (it's own roms folder by your screenshot) with the location that LaunchBox is pointing to and see if they are different.

Hi Martin, very nice work indeed. It's definitely got a neon feel to it and, since Vegas is neon city, how about Vegas Vegas Neon Neon Boneyard

Hi @dmjohn0x I've never used JoyToKey, but I have used XPadder and you can make a pair of Additional Apps per game to open a game profile before the game runs and close xPadder when you exit the game. Here is a useful link for XPadder: http://xpadder.com/forum4/viewforum.php?f=7 And here are example images for the 2 Add Apps. Your paths and game profile name will be different. And in the Edit Application Auto-Run tab for the Start XPadder Add App tick the Auto Run before Main App box for the Close XPadder Add App tick the Auto Run after Main App box

MAME also supports bezels, but you need to either source them or make them yourself. When you use MAME in the traditional sense for arcade games you can have a different bezel for each game. When you use MAME to emulate, say, the ColecoVision then you can only have one, common bezel and all your ColecoVision games emulated in MAME will use the same bezel - a platform bezel you could say.

Hi @legolas119 If you start LaunchBox and go to Tools, Options, Updates you will see 2 tick boxes. The box for Check for Updates on Startup should be enabled. If it's not, then tick it and click OK to save. You will now be notified on-screen if a new Official version of LaunchBox is available whenever you next start LaunchBox or BigBox. In between Official versions, the LaunchBox team also release beta updates and if you want to get those then tick the other box as well. When LaunchBox/BigBox does an update, it changes nothing to do with how you have setup your LaunchBox/BigBox. Everything will work as before, except for any new features or fixed bugs. When an update is done, LaunchBox (or BigBox) will automatically restart. Your License XML file just goes in the LaunchBox folder. You can go to Help, About, Premium to see the status of your License.

I only have the 180 version of that game umk3.zip and when I audited it with Mame 182 it failed due to 1 file missing 463 MK3 Ultimate.u64 If this is what is in your 181 update rom then you could extract it and add it to your 180 rom and try it out.

Hi @ckp The best way to find out a game's needs is probably to do an audit of the game. I believe that some of the Mame builds with a GUI can do this. I only use official Mame myself and it's audit tool is very basic, returning either OK or BAD. I use the EmuLoader frontend to do audits. For a list of Mame (180) Bios and Device roms see here. Mame180BiosList.txt Mame180DevicesList.txt

Hi @ckp So today I tested the 3 games using game and bios versions for Mame 180 with Mame emulator version 182 and all 3 games ran. I used the game roms (Mame 180 set) doapp.zip rvschool.zip sfex2.zip and the bios roms (also Mame 180 set) coh1002m.zip coh3002c.zip and Mame 182 to emulate. The actual 3 game roms haven't changed over recent Mame versions, but you do need the 2 bios roms for Mame 180 or later. Bios roms for Mame 179 or earlier will not work for these games when using Mame 180 and beyond.

Hi @ckp For the game doapp.zip the TPS bios is coh1002m.zip and it's contents (as of Mame 181) are m534002c-61.ic353 mg01.ic652 78081g503.ic655 For the games rvschool.zip and sfex2.zip the ZN2 bios is coh3002c.zip and it's contents (as of Mame 181) are m534002c-59.ic353 cp10.ic652 78081g503.ic655 The common file in the TPS and ZN2 bios is 78081g503.ic655 This file was added to the TPS and ZN2 bios roms in Mame 181 and is not in earlier versions. At the moment I don't have any information on possible Mame 182 bios or game changes, sorry for this. If I get it I'll post. For the full requirements of the three games as of Mame 181 see these images.

Hi @ckp I'm on Mame 179 myself, so game testing with Mame 182 is out for me at the moment. If your romset has been updated to 181, have you tried using Mame 181 to test these problem games? By the way, the ZN2 and TPS bios roms changed between Mame 180 and Mame 181 with the addition of a 3rd file (the common one I mentioned earlier). Perhaps they changed again for Mame 182, although I can't verify this. If you want to use Mame 182, your best option may be to update your full romset to 182.

Hi @ckp It's possible that the 3 games you mentioned may need to be updated. However, it may be more likely a BIOS issue. Two of these games use the ZN2 bios and one uses the TPS bios. These 2 bios have one file in common so that might be the issue.

Samples roms are used by some older games to add sound. For example without it's samples rom, Zaxxon plays with no sound. Best to grab a Samples pack, unzip it and drop all the zipped game samples into MAME's samples folder.

Hi @cheetahman91 If they were working and seem to have stopped, then check in your BigBox Options that your Platform List View is still set to Platform Wheel 1, and that your Videos are set to Use Platform Background Videos.

I'm on beta 6 and I just finished a lengthy testing of the audit feature. So far it works just fine with no crashes or errors. The only issue is that when it's first used after opening LaunchBox there's a bit of a wait before it goes into action. Subsequent audits run immediately. Mind you, I've seen this with other LaunchBox functions when I first use them. For example whenever I go to Edit Game I also get a delay, but after that the Edit Game opens promptly. By any chance was there an initialise-when-needed delay added to LaunchBox back when the big speed improvement in initial launching was brought in? Just curious.

I've also never had a need to use the %romfile% variable with any of my emulators, with the exception of blueMSX when I was testing it out with multiple Associated Platforms. It came in very handy then, as it allowed LaunchBox to pass the correct information to enable blueMSX to switch it's emulation mode to match the game's platform. By the way, Jason also added two other variables back then. Here are the three. %romfile% - gets replaced with the rom file path. %platform% - gets replaced with the platform name. %launchboxorbigboxexepath% - gets replaced with the EXE path to the running instance of LaunchBox or Big Box .

Yes, zipping a copy of the CHD file will also work, in fact anything (or nothing) can be put in the zip file. It's just something to get around LaunchBox not being able to be pointed to a folder, so an empty zip would be more practical memory wise, especially if the CHD file is very large. The golf one in question weighs in at around 1 GB. The empty zip file can be also just copied and renamed whenever you meet another of these CHD only games such as Chaos Heat or XII Stag.

Some while back Jason added the %romfile% variable to allow the use of parameters after the ROM file. I'm not sure if this is what you're looking for.

Hi @Soulnova In trying out MAME you need to go with a different game than the one you mentioned. Marvel Vs. Capcom 2 New Age of Heroes (Export, Korea, Rev A) - mvsc2.zip This game also needs The Naomi Bios - naomi.zip The MIE Device - mie.zip the JVS Device - jvs13551.zip The bad news is that you picked a game that doesn't currently work in MAME. With everything in place and setup correctly you'll probably only get as far as the Naomi logo screen or the Loading Game Now screen.

Hi @chrisg229. I can use blueMSX to launch both my MSX2 and ColecoVision game roms via LaunchBox. For an example, See my emulator setup images below. But I do prefer to use MAME with MESS.

Flip Box works fine for me with both the LaunchBox and BigBox interfaces. In LaunchBox, go to Tools, Options, Box Back Priorities and make sure the Box Back tickbox is enabled.