Kof 2000 Mame4droid

[Natalí Stibb]

AlsoI have a bunch of 0.37b5 ROMs for Mame 2000 that I had on my retropie that I want to use on Launchbox. Are there issues with compatibility or ease of use I'll run into by not using the mame emulator Launchbox recommends? I haven't tried it yet since I have to figure out how to setup my f310 Logitech controller with Windows 10 and launchbox first, but I have imported my ROMs and scrapped art. Launchbox/Bigbox made it super easy!

Update: At least I think I've found the answer to one question so far... After searching thru threads it appears CCS64 is a really good emulator for the C64, and that automatic fast loading feature sounds way better than Vice's in many ways, both in compatibility and auto turning it's self on and off by auto detecting game loading. Really slick.

I'm not too familiar with C64 emulation, but I have also heard that CCS64 is the best choice there. If you have a really old MAME set like that then your best bet for compatibility is to use the matching version of MAME. There may however be features missing in that version that are in the newer versions due to it's age. You can get that version here.

Thanks. My main concern with using Mame 2000 to run my 0.37b5 rooms that were meant for it is will I lose certain "ease of use" features Launchbox may do better in providing by using the version of mame they recommend? Meaning, am I going to lack controller pass thru configurations or some other potential features? Not even sure of what I'm asking exactly yet, as I have yet to delve that deep into just what LB offers in handshaking with emulators. I'm at the very superficial surface just starting now. Only thing I've done is import some ROMs and game art. Have to sort out the f310 controller setup before proceeding.

Launchbox has nothing to do with controls in emulators, that is down to the individual emulators, launchbox does not "passthrough" anything control wise. All launchbox does is open the emulator and tell it what game to load, nothing more. As for the version Launchbox suggests, it just that a suggestion, and its simply suggesting that version because it is newer. The thing you have to remember with mame is it is update constantly, as are the game zips themselves. You may find that as your games are so old that a lot of them simply will not work with the current version of MAME. That's why I suggest using the matching version, or simply getting more recent roms and then the matching version of MAME to go with them.

A question I have about the lb rom path setup for anybody out there...I hand made two folders in windows for some Commodore 64 games, one for all ROMs and one for hand picked ROMs that mainly are new better versions of games recently made of older C64 originals. I have yet to import either folder into Launchbox. What I'm wondering is how do I setup launch box to see both folders and yet keep them separate entities on the lb interface? I don't want to dump them both into one folder to direct CCS64 to.

A question I have about the lb rom path setup for anybody out there...I hand made two folders in windows for some Commodore 64 games, one for all ROMs and one for hand picked ROMs that mainly are new better versions of games recently made of older C64 originals. I have yet to import either folder into Launchbox. What I'm wondering is how do I setup launch box to see both folders and yet keep them separate entities on the lb interface? I don't want to dump them both into one folder to direct lb to.

You can simply name the systems slightly differently when importing and point them both to the same emulator. The default in the dropdown is "Commodore 64" so use that for your full set, then for the other instead of using the dropdown you can actually type into the box. So for example you could call it "Commodore 64 New Games" and as that is not a default system name you will be asked what to scrape it as, just say Commodore 64 again. So you would then have two C64 systems imported, one called "Commodore 64" and another called "Commodore 64 New Games" (or whatever you want to call it).

Just figured out Mame 2000 won't run on my 64 bit windows 10 even in compatibility mode. That means my rom collection is useless. Might as well use latest Mame then and put together the appropriate ROMs for it. Now to figure out how to limit those ROMs to 1980s and 1990s.

Also ran into another snag for Commodore 64 setup. For some reason import on launchbox isn't offering me the little dark blue link that I can click on to search elsewhere on the web for the emulator I want. I'm guessing I can just manually use chrome to go get ccs64 and stick it in the right folder, and then go thru the import steps?

Sounds like the plan. Thanks. Haven't owned a Windows computer in years. All my experience has been Android as of late, and far as retro gaming setup it's only been on the pi 3 using Retropie, so relearning windows and also sorting thru lb setup is going to be a project. I thank all of you for the help.

Thanks. Just copied that for future reference. And far as lb launch commands go, I believe when importing emulator setup you enter the command line -fullscreen so it launches the emulator that way? Wondering if ccs64 defaults to a good aspect ratio or if there's a prefered one for a large screen?

Just a small update: I switched to Vice for Commodore 64 Emulation. The CCS64 Emulator was giving me a few issues, such as a glitch causing it to try to load bad file names when I'd launch games via LB, etc. This was only after successfully LB launching a few games that it began to happen. Even games I had just loaded ten minutes prior with no problem would now cause the dreaded Commodore 64 "bad syntax" or no such file found error. I wasn't particularly impressed with it's interface either, and found that it was causing certain games to input ghost responses as well (such as making Mario walk left when I wasn't touching the joystick).

So I erased the emulator and installed Vice in LB, and every single issue above has been fixed. I'm sure CCS64 is a great emulator, and the auto fast loading/auto deactivation really is great, but I didn't feel like digging into why I was experiencing such problems. Vice has been smooth sailing thus far. I much prefer the interface, and I guess I'll just put up with having to press Alt W to fast load and then pressing it again to deactivate it. I'm guessing I can assign that to a button on my F310 joystick, just not sure yet if I can do that through Vice or need to use some 3rd party key mapping app. I'll look into that later. Time to play a few games. Any other assigned keys to joystick buttons that people seem to like would be of interest too, such as spacebar, F1, Y, N, etc.

The file name thing isn't CCS64's fault - it's LB's. Certain characters in a filename cause issues for CCS64 when they're launched via LB (while the same file will work just fine when started within CCS64 itself). Certain things like brackets, double parenthesis, commas, and plus or minus signs in the filenames seem to cause issues. Any time you encounter that you can just rename it to something simpler and it'll work fine.

The control thing just sounds like you need to calibrate your joystick in the Input section. I've never had any issues with erroneous inputs unless you have the same input device (like a controller) connected to both port 1 and port 2 at the same time (which you should never do). You want to associate it with one port, and switch between them as needed (and I have an AHK script to add that, among other things, to a controller).

Ahhh...I did have the joystick active on both ports, so that was probably the issue. So far Winvice has been flawless, but wondering if same deal of activating joystick for both ports can cause issues with certain games.

Also wondering in Winvice, how do I set it for full screen to block out background screens, yet have the It retain the proper non HD aspect ratio of a Commodore 64? Meaning, not have it stretch the game to HD proportions.

03 APRIL 2024Added various cheats posted on the forums and some cheats I've made, and obviously the normal maintenance stuff.Here is the cheat collection update for the latest MAME (0.264).XML/JSON Cheat Collection for MAME 0.264 [3884K]

Note: The XML/JSON Cheat Collection archives are double packed. Inside the downloaded zip archive you will find a large cheat.7z. It's this cheat.7z that should be placed in the same directory as your MAME execute-able.Read the cheat.txt file contained in the cheat0264.zip for more information. If you spot any errors (non-working cheats or parsing errors) then please post them in this forum topic .

06 OCTOBER 2023Another maintenance release, added various cheats posted on the forums (mainly from Abystus) and some cheats I've made.Here is the cheat collection update for the latest MAME (0.259).See the MAME Cheat Files section for a link for this version which has now been superceded.

Similar maintenance release to this time, although I've also made cheats for most of the Exelvision EXL 100 software list games and I've started to make cheats for the Amstrad GX4000 software list games.Here is the cheat collection update for the latest MAME (0.257).See the MAME Cheat Files section for a link for this version which has now been superceded.

This is more or less a maintenance release, although there are now cheats for most of the Mega Duck software list games.Here is the cheat collection update for the latest MAME (0.256).See the MAME Cheat Files section for a link for this version which has now been superceded.

3a8082e126