exporting_gamebases_to_other_frontends
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | exporting_gamebases_to_other_frontends [2023/10/04 14:15] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Exporting GameBases to Other Frontends ====== | ||
+ | |||
+ | This page shows you how to get GameBase databases to run on arcade/ | ||
+ | |||
+ | ===== Why? ===== | ||
+ | |||
+ | This all came about because I wanted to run some GameBase databases on my Arcade Cabinet. | ||
+ | |||
+ | Lets say, like me, you have built, or aquired an Arcade Cabinet, or a " | ||
+ | |||
+ | **Why not just run the emulators directly from my arcade frontend?** Good question. For many of the more popular GameBase databases, such as GB64 and GameBase Amiga, a load of work has been done to get the games running in the emulators as best as possible, with all the correct settings and controls. Emulators can be fiddly things, and some games just refuse to play ball unless everything is configured perfectly. GB64 and GameBase Amiga are great examples of this. So, by using GameBase (or more specifically GEMUS) to run the games, you're getting rid of a big potential headache, and saving yourself countless hours trying to figure our why game X doesn' | ||
+ | |||
+ | **Why do I need GameBase databases on my cab?** Well, you don't really need them, but since *I* needed them, I thought there might be others out there with the same desires. Going back to the popular GB64, there' | ||
+ | |||
+ | ===== How? ===== | ||
+ | |||
+ | There are 2 stages involved: | ||
+ | |||
+ | - Convert your GameBase data into the format understood by your chosen arcade frontend. | ||
+ | - Setup your arcade frontend to launch the games using GameBase' | ||
+ | |||
+ | === You will need === | ||
+ | * The GameBase frontend v1.3 or newer must be installed on your system | ||
+ | * Your chosen databases must be setup correctly in the GameBase frontend | ||
+ | * [[http:// | ||
+ | |||
+ | === Supported Frontends ==== | ||
+ | As of build 021 of RomLister: | ||
+ | * Atomic FE | ||
+ | * HyperSpin | ||
+ | * Khameleon | ||
+ | * MaLa | ||
+ | * MAMEWah | ||
+ | * Maximus Arcade | ||
+ | * MultiFE | ||
+ | |||
+ | ===== Exporting from GameBase ===== | ||
+ | |||
+ | === Select the View to Export === | ||
+ | First step is to export your current view in GameBase, so load up your chosen GB database, and select the view you wish to export. You can export multiple views from GameBase, for example on my cab I exported the <All Games> view and the < | ||
+ | |||
+ | === Export the View === | ||
+ | Once you have your view displayed (only the list of games is important, the 2nd column is ignored as all needed data is read from the database during the export), select " | ||
+ | |||
+ | == Screenshots == | ||
+ | You'll also want to tick the " | ||
+ | |||
+ | === Exported Files === | ||
+ | When finished exporting, you should have a new folder full of renamed screenshots and an XML file containing the exported view's data. The XML file will be in your GameBase frontend folder and will be named in this format: | ||
+ | |||
+ | [database-name]-[view-name]-(Game ID|Filename)-romlister-export.xml | ||
+ | |||
+ | In my case it was: | ||
+ | |||
+ | GameBase Amiga-All Games-(Game ID)-romlister-export.xml | ||
+ | |||
+ | ===== Creating Gamelists in RomLister ===== | ||
+ | |||
+ | Fire up RomLister and set the Input XML File to the exported one that GameBase just generated. Then all you should need to do is click " | ||
+ | |||
+ | **Filtering in RomLister** - You can't use *all* the filtering stuff in RomLister, as the exported XML file from GameBase doesn' | ||
+ | |||
+ | ===== Configuring your Arcade Frontend ===== | ||
+ | |||
+ | I've only configured MaLa (that' | ||
+ | |||
+ | === Using GBLauncher.exe === | ||
+ | |||
+ | In MaLa, I chose GBLauncher.exe (it's in the GameBase frontend folder) as my emulator executable, I didn't assign a Rom Path (GBLauncher handles that!) and the command line I set to: db=" | ||
+ | |||
+ | This tells MaLa to run GBLauncher.exe as the emulator, and pass to it the database name (GameBase Amiga), the %rom% (which MaLa grabs from the gamelist) as the GameBase game ID, and the wait flag (we want GBLauncher to wait until the emulator it launches has closed before quitting and returning to MaLa). | ||
+ | |||
+ | So the command line arguments for GBLauncher are as follows: - | ||
+ | |||
+ | * // | ||
+ | * // | ||
+ | * // | ||
+ | * // | ||
+ | |||
+ | [[GBLauncher.exe|Full GBLauncher.exe Documentation]] | ||
+ | |||
+ | === Guides for other arcade frontends === | ||
+ | |||
+ | * [[exporting_gamebases_to_maximus_arcade|Maximus Arcade]] (by SkydivinGirl) | ||
+ | |||
+ | === Other Configuration === | ||
+ | |||
+ | If you're running on an arcade cabinet, or using real arcade controls, you may need to tweak the GEMUS script of your chosen emulator to get it running correctly, mapping keys to joysticks, setting arcade monitor resolutions etc. I used a small program called [[http:// | ||