[General Topics] Menneisyys:
CPS-2 titles, links & compatibility reports

1944: a really good 1942 clone! A must have!

19xx: another excellent 1942 clone, works great even at 44kHz! Another must have!

Alien vs Predator: fighting, not that good IMHO

Armored Warriors : not very good either

Battle Circuit: side scroller, not very interesting

Dimahoo: too, another good 1942 clone (not as good as 1944 / 19xx though)

Eco Fighters: side scroller, not very interesting; you still might want to give it a try

Night Warriors: typical Street Fighter clone

All these games run flawlessly, mostly with 44 kHz sound, on the x51v – and even on the HTC Wizard (with, particularly with 19xx, 8 kHz sound). The 520 MHz WM5 VGA HTC Universal is pretty bad (very slow) for emulation, so is the 624 MHz WM5 (2.01) VGA HP iPAQ hx4700 (which is only a tad better and DOES require and external BT game pad because of the completely gaming-unfriendly touchpad). The WM2003SE VGA Fujitsu-Siemens Pocket Loox 720 is acceptable (but, of course, visibly / audibly worse than the x51v), so is the WM2003 QVGA HP iPAQ 2210.

Also note that FinalBurn Alpha supports (almost) all CPS games, unlike with the case of NeoGeo.

Using the emulator I – starting games

The desktop and the WM versions of the emulator are, fortunately, pretty similar. This means if you learn how, for example, the ROM selection screen works, what the main directories of the emulator are etc. in the desktop version, you will also be able to utilize this knowledge under WM.

Starting the emulator is pretty easy: just start the main executable file (after decompressing it anywhere (under Windows Mobile, preferably to a memory card because it’ll look for the ROM images in a subdirectory) and, with the debug desktop version, also adding kailleraclient.dll): fba.exe with the official desktop FinalBurn version, fbaud.exe with the cache-generating debug desktop version and FinalBurn.exe on the Pocket PC.

When first run, the executable file will also create the necessary directory structure, including the ROMs subdirectory. You can start putting your ROM games in there (and, of course, Neogeo.zip containing the NeoGeo BIOS if you do want to play NeoGeo games). Under WM, you’ll be presented the following screen:

Here, go to File / Load Rom. It’ll present a long list of all games compatible with FinalBurn. You don’t necessarily want to see this list but only the accessible AND compatible games; therefore, you will need to tick in the “Show Only Available” checkbox at the top. Now, the listing will become far more manageable as it will only list the games that you can run:

By single-clicking an item in here, the emulator starts it after creating a so-called ‘cache file’ as can be seen in here.

Creating cache files can be a real nuisance. If you do this on your handheld, it may take quite a time (1-2 minutes at most; if it takes more time, you can be pretty sure your handheld has crashed and needs to be reset). Furthermore, with ZIP files exceeding 50-60 Mbytes (for example, the excellent platformer Metal Slug 3, which is a whopping 79Mbytes), all your dynamic RAM memory (independent of the available free memory on your storage card or internal storage) will be all quietly consumed and the handheld will either crash (as is pretty common with WM5+ in these cases) or just display it has run out of memory (with WM2003(SE)).

Therefore, if you do encounter such situations, you will want to create the cache images on the desktop Windows, using the above-introduced debug cache-creator version of FinalBurn Alpha. To do this, just start fbaud.exe (after copying neogeo.zip and the ROM image ZIP of the to-be-converted game to the ROMs subdirectory), go to Game / Load Game (F6), select the game you’d like to convert (screenshot here; I’ve also made sure to hide non-available titles by ticking in “Show Available Only” (see the mouse cursor) and click OK. The cache file will be created and named exactly the same as with the ROM ZIP file name – with the extension “cache”. That is, for example, if you create a cache file of the unencrypted Metal Slug 3 (mslug3n.zip), the related cache file will be named mslug3n.cache. It’ll be put in the “cache” subdirectory of the desktop emulator. Make sure you copy this file to the memory card, in the same ‘cache’ directory. It’s also here that other cache files are stored.

By the way, don’t forget to delete partially created cache files from this directory (that is, files that weren’t finished because of the dynamic RAM memory or the storage card getting full). Messed up cache files are the main reason for messed-up graphics in the emulator.

Now, after having created the cache file, the game will start. You will, however, need to do some additional configuration to be actually able to play games. This will be needed to done only once – fortunately, the configuration options you make will be stored in the cfg directory. BTW, these files are all human-readable and editable; they contain the game-specific button settings. That is, the ones you’ll always need to set up.

The first step in making the games playable, after loading them, is setting up the hardware buttons.

Using the emulator II – setting up the buttons

After you’ve loaded a ROM image (and clicked the screen so that the execution stops and the menu is displayed), you must go to Options / Keys. It’s there that you must assign hardware buttons to functionality.

Doing this is pretty simple: you click an on-screen button and, then, press the hardware button you’d like it to be assigned to. For example, click the Coin and, after this, click a button you’d like to use to simulate feeding money into the arcade machine (the first step in starting a game; after this, you’ll also need to press the Start button). You will also need to assign the A, B, C and, with NeoGeo, D hardware buttons too. (These will have different functionality: for example, in Metal Slug, firing, jumping and throwing a grenade. Button D isn’t used.) Note that the emulator also supports WM5 hardware soft keys as can also be seen in the screenshot below (C and D buttons). If your mobile has a built-in keyboard, you can also use most (not only alphanumeric) keys on it.

You will also need to set up the D-pad directions; always treat the D-pad in Portrait mode, even if the game itself is in Landscape.

You can also tick in the “Enable Auto-Fire” checkbox if you want auto fire; remember, however, that it, currently, only works with CPS games, NOT with NeoGeo ones, unfortunately.

A typical screenshot of setting up the hardware buttons is as follows:

Finally, keep in mind that you can only set up the buttons for Player 1 in here. Should you also want to set up the Player 2 buttons, you will need to edit the game configuration file in the cfg subdirectory.