Adding Sega Lindbergh Arcade Platform

[stonev]

Hi All--As some of you may know, a new windows-based Sega Lindbergh emulator was released a few days ago, based on the linux-only "Lindbergh Loader" emulator. I'm not sure if I'm allowed to post the Github link here, but it should be simple enough to find. In any case, it works amazingly well so I'd like to integrate the working games into LB, but I'm not sure where to start. In the past, I've relied on the amazing work of @Warped Polygon but given that the emulator was only just released, I expect it to take a little time.

The games aren't traditional single ROM files. The easiest way (for me) to play is to create a batch file for each game which points at the game directory, the general ini file, and the general control file.

So if you've already done this, I'd be interested to know how you approached it. And if not I'd still be happy to take some advice!

Thanks for any insights you can provide.

[stonev]

Ok, I've been playing around and this process seems to work for me:

1) Create Sega Lindbergh platform. The platform doesn't seem to exist by default, so you need to create it. For now, you can just create a bare-bones entry and add more details later. All I did was go to Tools > Manage > Platforms and clicked Add... On the Details tab, I entered Sega Lindbergh under "Title" and Arcade under "Scrape As" and clicked OK.

2) Add Games. Remember, I'm using .bat files to launch these games. So I went to Tools > Import > ROM Files. Click Next and the Add Files. I added my .bat files here. and clicked Next. I selected the Sega Lindbergh platform I created in the previous step (ensuring "Arcade" is listed under "Scrape As". I left the emulator blank and clicked Next. I then selected "Use the files in their current location". I unchecked Search for game info and Check None for any media downloads.

3) This created a new Sega Lindbergh platform category under Arcade and the game I added in the previous step showed up there. At this point I could go into the entry and edit Metadata/Media. First, of course, in the Metadata section I searched for the actual game title in the LB Database. Then, in the Launching > Emulation section, I unchecked "Use an emulator to play this game".

4) Download Media. Once the correct game was tagged, I went back and downloaded the game media: Tools > Download > Update Metadata and Media for Selected Games and went through the normal process of downloading media from LB and EmuMovies.

And that's mostly it! I also went back and added more info to the Lindbergh platform entry from here:

I also added clear banner from here to replace the default Arcade banners:

I hope this helps folks get started. Happy gaming!

[Warped Polygon]

On 5/11/2026 at 12:30 AM, stonev said:

Hi All--As some of you may know, a new windows-based Sega Lindbergh emulator was released a few days ago, based on the linux-only "Lindbergh Loader" emulator. I'm not sure if I'm allowed to post the Github link here, but it should be simple enough to find. In any case, it works amazingly well so I'd like to integrate the working games into LB, but I'm not sure where to start. In the past, I've relied on the amazing work of @Warped Polygon but given that the emulator was only just released, I expect it to take a little time.

The games aren't traditional single ROM files. The easiest way (for me) to play is to create a batch file for each game which points at the game directory, the general ini file, and the general control file.

So if you've already done this, I'd be interested to know how you approached it. And if not I'd still be happy to take some advice!

Thanks for any insights you can provide.

Hi mate, I haven't had an opportunity to take a look at this Linux Loader. Looks awesome, before I do anything preconfig wise I let the emulation or project mature a little. Quite often I've configured/QoL something for it to then be handled at emulator level a week later. This is always something to factor but more so in the early phase. I hear there's a UI in the works for it.

But what you have done here should stand as it's at command line with bat files. I'm sure the community would like to get their hands on those right now!

[stonev]

Your instincts are good! There’s a point update almost daily so, yes, it will take some time to settle. I think I’m just really impressed at how well it worked out of the box (although there has been plenty of development on the Linux version). For those interested in playing around, I would definitely suggest joining the Discord that is linked on the GitHub page. Although setup is relatively straightforward, the rom files need to be “clean” and some folders and files need to be renamed in order for some games to work.

Hopefully it won’t be long until it’s a little more stable and a UI is released. In the meantime, I’ll keep playing…

[launchretrogirl2562]

On 5/13/2026 at 3:00 AM, stonev said:

Your instincts are good! There’s a point update almost daily so, yes, it will take some time to settle. I think I’m just really impressed at how well it worked out of the box (although there has been plenty of development on the Linux version). For those interested in playing around, I would definitely suggest joining the Discord that is linked on the GitHub page. Although setup is relatively straightforward, the rom files need to be “clean” and some folders and files need to be renamed in order for some games to work.

Hopefully it won’t be long until it’s a little more stable and a UI is released. In the meantime, I’ll keep playing…

are the roms for lindbergh the same as the ones for teknoparrot?
and what are these bat files u mention? Can u post an example of them?

[stonev]

I’m happy to post a bat file, but there’s really nothing complicated beyond following the GitHub Windows Guide. Just:

linuxloader.exe -g “path\to\game” -c “path\to\config\ini” -o “path\to\controls\ini”

I just made the batch files because it was easier than typing.

The TP roms will NOT work. Apparently, they are not “clean” dumps and have been specifically modified to work with TP. I can tell you that the “clean” roms have been archived on the internet, though.

[sucramjd]

They do work, well some do i tried outrun and afterburner climax both loaded up and played, but your supposed to use clean dumps. I like it seems good so far early days yet though. I made a really simple ahk instead of bat files because I want to launch demulshooter and hotr. You need to put both .ini files where the games .elf file resides or it doesn't load really easy once you get the hang of it.

[sucramjd]

Ahk works fine

 

[stonev]

22 minutes ago, sucramjd said:

You need to put both .ini files where the games .elf file resides or it doesn't load really easy once you get the hang of it.

The game folder is one of the default places to put the ini files, but it’s not 100% necessary. I keep my files in my Linux Loader folder and use the same file for multiple games. As I mentioned, you can use the -c option to specify the relevant main ini file and the -o option to specify the relevant controls ini file.

Since these are still early days, updates come pretty fast and often add new ini settings. It’s a lot easier to change 1 file than 1 file per game.

[sucramjd]

Just tried outrun seems fine first play through, soon as I exit and restart gets all choppy and unplayable do you have this problem?

[JoeViking245]

I like to keep it a little cleaner without the use of batch files for each game. 

What's working for me is to add the emulator to LaunchBox just like normal.

• For the few games I've tested, they all work using a single ini file
  • No special per-game changes needed
  • Named mine linuxloader.ini (as shown above). Can rename yours to whatever_you_want.ini
• This ini file gets located in the same folder as the emulators executable
  • Requires version 3.0.6 or newer. 
    • Otherwise you need to put -c "full\path\to\linuxloader.ini"
    • Or.. copy linuxloader.ini into each of the games' folder containing its .elf file

 

Then for the game's ROM file path, point to the game's .elf file (not just the folder). This alleviates the need for the -g parameter in the Default Command-line Parameters.

Since there's only a handful working at this point, don't expect or go looking for an automagical way of adding these. Just drag & drop each game's .elf file onto LaunchBox and let it add the game.  Yes. It will need to be done one-at-a-time.

 

If you have a need to load a game-specific ini file (configuration and/or controller), in the game's Emulation section, you can check the box and add the parameter(s) there.

 

 

To get the most out of the lightgun games, I'll start QMameHook and just let it run in the background, behind-the-scenes.  (Use your hooker of choice).  Then with the help of the DemulShooter Auto-Launcher plugin, DemulShooter loads automatically as needed when launching a game.

 

My shameless plug:

 

[stonev]

30 minutes ago, sucramjd said:

Just tried outrun seems fine first play through, soon as I exit and restart gets all choppy and unplayable do you have this problem?

I haven’t had this problem, fortunately.

[stonev]

Thanks, for the step-by-step, Joe! The reason I went with bat files instead of your straightforward method is that I couldn’t always find an elf file in each game. I’ve got one for Too Spicy, Initial D 4, and HOTD 4, but not Afterburner, GSE, LGJ, or Virtua Tennis. So I only have a game path to reference. Apparently, LL finds whatever file(s) it needs at the end of the path. Or am I being to literal by only looking for files with .elf extensions?

[stonev]

Check that. Discord help pointed me to this file:

https://github.com/lindbergh-loader/linuxloader/blob/main/src/loader/mainShared.c
 

I think it shows which file is the executable for each game. I’ll see if I can use these in LB and set it up like Joe suggested.

[JoeViking245]

8 minutes ago, stonev said:

Apparently, LL finds whatever file(s) it needs at the end of the path

It does. Which is a nice command line feature.  But now very front-end friendly.

This shows what elf file it's looking for. For each game:  Lindbergh Loader - EmulatorEggs

For gsevo, it didn't have a .elf file (as you mentioned).  Let alone an "abc.elf" file ("abc" as found in the link above).  Getting lucky I copied a file named "vsg" and renamed it to "abc.elf" and used it.  It worked.

 

For kicks and grins, I just tested:  for hotd4, I renamed "hod4M.elf" to "joe.elf" and set the ROM path (in LaunchBox) to it.  It also worked.   Getting more crazy, I removed the file extension from the file and pointed the ROM path to "/path/to/joe". That worked too.  

So, by all rights, for gsevo, point the ROM path to the file "vsg".

[stonev]

Quote

If you have a need to load a game-specific ini file (configuration and/or controller), in the game's Emulation section, you can check the box and add the parameter(s) there.

Joe, I’m curious about how LB deals with this. For hotd, I use the default control file but have a separate settings file (using custom crosshairs and setting CPU speed), whereas for LGJ, I use the default settings file, but have a custom controls file (to invert the mouse movement).

So for hotd, if I use the game’s emulation section to set the control file, does it overwrite the default -c linuxloader.ini or append to it? If the former, then I’d think I’d need to add the -o option *and* the -c option in the game’s emulation section. If the latter, then just the -o option. Similarly, for LGJ, if I just add the -o option, what happens to -c linuxloader.ini specified in the emulator settings?

[JoeViking245]

26 minutes ago, stonev said:

if I use the game’s emulation section to set the control file, does it overwrite the default -c linuxloader.ini or append to it?

It completely replaces the Default Command-line Parameters.  Just like it does when you add command-line parameters in the Associated Platforms section when editing an emulator.

 

So you need to re-add -c linuxloader.ini and append -o myHOTDControls.ini

 

If all goes well, it'll load linuxloader.ini, found in the same folder as linuxloader.exe.  And as was not noted above, it will look for myHOTDcontrols.ini in

1. the same folder as linuxloader.exe
   • if not found, then looks in...
2. the same folder as the ROM (.elf) file

From v3.0.6 and newer, it looks for the files in that order (if no path/to/file.ini is given).  From the changelog:

- Changed the default behavior of -c, -o and -d to not load from the game folder 
by default if no path is specified. Now, if you pass just the filename, it will 
search in the current directory, then will fallback to the game folder, 
if not found there, it will use the default config.

[stonev]

Got it. I decided to pass "-c linuxloader.ini -o controls.ini" as default command line parameters for the emulator. For HOTD4, I use custom command line parameters, "-c linuxloader_hotd4.ini -o controls.ini" and for LGJ, I do the same "-c linuxloader.ini -o controls_lgj.ini"

It works great and feels a LOT better than just using .bat files. Thank you for the mini guide!