Jump to content
LaunchBox Community Forums

stonev

Members
  • Posts

    33
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

stonev's Achievements

8-Bit Processor

8-Bit Processor (3/7)

10

Reputation

1

Community Answers

  1. 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!
  2. 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?
  3. 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.
  4. 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?
  5. I haven’t had this problem, fortunately.
  6. 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.
  7. 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.
  8. 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…
  9. 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!
  10. 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.
  11. Thank you for the really, really, thoughtful response @JoeViking245. I *knew* that this wasn’t a simple thing (otherwise it would have been implemented already), but it’s helpful for me (clearly not a dev) to get your perspective. I’ll keep thinking on it, but in the meantime, I’ll enjoy playing Outrun 2006 without having to pull out the keyboard!
  12. Well, @JoeViking245, you’ve saved me once again! Thank you, Internet friend, this worked perfectly. I’d be interested to hear your thoughts on a possible LB enhancement request to deal with this (admittedly solvable) problem: In the Additional Apps settings, could you have a checkbox option to close the additional app after the game stops running? Would that be something relatively easy for devs to implement? Would it even be worth it? Are there complexities in that process I’m not considering? Again, thank you!
  13. Ok, this should be fairly simple but it's been driving me a bit insane: I've got the PC version of OutRun 2006 set up exactly as I want it. The only tweak I can't make within the game is to remap my "Start" button (1) to [Enter] and my "Coin" button (5) to [Escape]. Enter and Escape are the main ways to move around the OutRun menus. So I set up a very simple AHK script: 1::Enter ; Start button 5::Escape ; Coin button Works perfectly! I can now navigate the game using only my buttons. The only problem is that when I exit the game, the AHK script (and the re-mapping) persists. I'd simply like for the script to exit when I exit the game. So are there additional lines I can add to this script to accomplish this OR is there a generic "Kill AHK" script that I can add to my Additional Apps for this game (and other ones)? In the past, I've linked killing the script to the generic game exit button (Esc), but I'm not sure that will work here since Esc isn't the immediate "kill game" button like in RetroArch and Mame. Any help would be appreciated!
  14. Ok, so I peeked in at the AHK forums and yet another helpful internet friend tweaked the code so that the LCtrl variable issue is fixed AND the script works for a second player! Holding down the fire to get a powered attack while autofire is on can be hit-and-miss but I don't think that's fixable given the absolute barrage of button presses the game has to take in. In any case, for anyone who finds this, here's the working script: ; --- Configuration --- SetKeyDelay, 0, 50 ToggleKey1 := "LShift" ; Key to turn P1 autofire on/off FireKey1 := "LCtrl" ; The P1 button to spam (Left Control) ToggleKey2 := "w" ; Key to turn P2 autofire on/off FireKey2 := "a" ; The P2 button to spam (Left Control) Interval := 50 ; Milliseconds between fire button presses (adjust for speed) ; --- Variable --- AutoFire1 := AutoFire2 := false ; Start with P1/P2 autofire off ; --- Toggle Hotkey --- Hotkey, %ToggleKey1%, ToggleAutoFire1 Hotkey, %ToggleKey2%, ToggleAutoFire2 ; --- Main Autofire Timer (Controlled by the toggle) --- Hotkey, ~%FireKey1%, FireKey1 Hotkey, ~%FireKey2%, FireKey2 Return FireKey1: ; When the P1 FireKey is pressed down (~) If (AutoFire1) { ; If P1 autofire is ON Send,% "{" FireKey1 "}" ; Press the P1 fire button SetTimer, FireKey1, -%Interval% } Return FireKey2: ; When the P2 FireKey is pressed down (~) If (AutoFire2) { ; If P2 autofire is ON Send,% "{" FireKey2 "}" ; Press the P2 fire button SetTimer, FireKey2, -%Interval% } Return ; --- Function to Toggle --- ToggleAutoFire1: AutoFire1 := !AutoFire1 ; Flip the P1 state (true to false, false to true) SoundBeep, (%Autofire1%+1)*250 Return ToggleAutoFire2: AutoFire2 := !AutoFire2 ; Flip the P2 state (true to false, false to true) SoundBeep, (%Autofire2%+1)*250 Return ; --- Exit Script --- Esc:: { WinClose, ahk_exe mame.exe ExitApp } Happy gaming!
  15. A little update: I tweaked the original exit script: $Esc:: { WinClose, ahk_exe mame.exe ExitApp } ..and removed the "$" so now it's just Esc:: { WinClose, ahk_exe mame.exe ExitApp } ...and this seems to work. Would there be any unforeseen consequences of removing the "$" that might make this change inadvisable? Also, I got rid of the Tooltip code and replaced it with: ; --- Function to Toggle --- ToggleAutoFire: AutoFire := !AutoFire ; Flip the state (true to false, false to true) SoundBeep, (%Autofire%+1)*250 Return Now there's an audible beep when I toggle AutoFire on and off. The tone is higher for "on" (500hz) and lower for "off" (250hz).
×
×
  • Create New...