Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    5,127
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by JoeViking245

  1. It looks like you're using the Old Default theme. Though not sure switching to Default will change anything. You might could try... In your v13.27 LaunchBox install under /LaunchBox/LBThemes/, create a new folder called Old Default 13.15. Then from your v13.15 install, copy the contents of /LaunchBox/LBThemes/Old Default/ into the new folder you created. Then go to Tools < Options < Visuals < Main Window Theme and select Old Default 13.15 and see if that works like-you-like.
  2. What theme are you using? And what version of LB?
  3. Tools < Options < Visuals < Boxes -- un-check the box Dynamic Box Sizing.
  4. There was an issue with a release [about 2 versions ago] where the notification wouldn't show. It has since been fixed. You can manually check for updates (which if you're on "that version", that's what you'd need to do) by clicking the 'hamburger' Menu < Help < Check for Updates...
  5. If the bezel's going fullscreen and the emulator window is "inside" the bezel, no. Try checking the parameters g and h (in BezelLauncher Setup and see if that helps. If that doesn't help, can you attach the corresponding Log file [e.g. the most recent log file in the plugins Logs folder. The file will start with "log". Not "SetupLog"].
  6. Anytime an error code like that appears, it's one of three situations: 1. The license is banned 2. The license has been altered (you tried to change details in the file, or the file has been corrupted). 3. You are using an Android license on PC or vice versa aka: The error indicates something is up with your license file. Email support@unbrokensoftware.com and they can sort it out for you.
  7. Since Xenia Manager is not an emulator itself, you might try setting up in LaunchBox the emulator you setup inside Xenia Manager. (Similar to how it's shown several posts up.)
  8. 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 the same folder as linuxloader.exe if not found, then looks in... 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.
  9. 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".
  10. 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:
  11. v1.2.0 Released Added Linux Loader as a supported emulator for Lindbergh games.
  12. That location has been depreciated. They are now stored below \LaunchBox\Images\Media Packs\ You can read more about it here: Media Packs - LaunchBox
  13. Pretty sure all of the Steam Lego® games, when in 2-player mode, will split the screen [when the 2 characters are far enough apart]. Years ago, I saw a prototype for a Big Box plugin that would allow you to launch 2 to 4 games at once and would split the screen accordingly. e.g. 4 games would split the screen into quadrants (top left, top right, bottom left, bottom right). They could be the same game or 4 different games. Setup was not for the faint of heart. A bit of manually modifying your Big Box theme(s), having 4 complete installs of the emulator(s), and a bunch of other pre-configuring. The "4 complete installs" were installs on your hard drive. You couldn't just add e.g. the same install of RetroArch to LaunchBox 4 times. Early testing showed that it was working well. But the author, unfortunately is no longer around.
  14. It will only delete (remove) the "GAMES from your [LaunchBox] collection". "Collection" being the games you have installed in LaunchBox. (I guess that can still sound confusing. ) It will not delete the ROMs from your computer. UNLESS you check the box under Tools - Options, "Allow deleting ROMs when deleting games". This is un-checked by default. Also, if it were checked and you went to delete a game or platform, a 2nd popup message will show:
  15. Thanks for confirming. The LaunchBox development team is looking into it.
  16. To clarify (for the developers when they read/look into this), is it "Minimized"? Or is it "behind" the Main LB window? To test, pop-out the game details panel then click the - (minus symbol) in the upper right corner of the main LB window to Minimize it. If the pop-put windows is 'there', then it's just going behind the LB window. If not, it's [probably] minimized.
  17. With your mapdevice.cfg file, it shouldn't matter which USB port they're plugged into because you're referencing the device by its ID. If you wish (works either way, but doesn't explain why it was, then wasn't and is now working), you can truncate your 2 lightgun ID's in your cfg file. e.g. <mapdevice device="VID_0483&amp;PID_5750 controller="GUNCODE_6" /> <mapdevice device="VID_0483&amp;PID_5751 controller="GUNCODE_7" /> For the other 2 GUNCODE_6 and 7, between your Log and your cfg file, there's an extra 0 (zero) at the end of the instance in the cfg file. Not sure if it makes a difference or not. cfg file 4445535400000 Log file 444553540000 Regardless, glad it's working now.
  18. Version 1.0.1 This release is being published here only and will be added to the 'official' download at a later date. MAMEtools (v1.0.1).7z Which MAME Machines Require CHD's New Feature: Added Export to file button Save-to options comma delimited .csv file .txt file with ROM - Game Title .txt file with ROM - Game Title - Parent ROM - Status File will be saved to the plugins' folder as CHD-list.csv (or CHD-list.txt) CHD-list.csv CHD-list.txt CHD-list.txt
  19. From the Windows Command Prompt, run the command "mame.exe -v" and read through the verbose output. It should show the devices is whatever order, then later indicate it's loading your mapdevice.cfg file and (re)setting the order.
  20. Check that it's still in the /Plugins/ folder. Should be something like /LaunchBox/Plugins/MultiMonitor/MultiMonitor.dll. Verify it's unblocked (as mentioned under Installing:). There should also be [something like] a settings.xml file in there (if was setup once before). ('settings' name may be something else. But will be an xml file). iirc
  21. TBH, I haven't looked at this in almost 2 years (the last plugin update). Did you try... Click Tools, MultiMonitor Setup?
  22. Which one? A comma delimited text file with the 4 fields? A text file showing just the ROM filename and Title? Or you going to the Arcade Database site and generating one from there? A sub-note from yesterday: When exporting the results from the ADB site, if you select CSV (csv), the output will be in a comma delimited format and will have 20 columns of datum (including, but not limited to Year, Manufacturer, Display, Driver and Source file). A sub-sub note: To see these CHDs "hands on"... Open the MAME Custom xml Importer feature Browse to the plugins Data folder and select the file MAMEchds.xml For the platform, select Add new Platform it'll be called MAMEchds Import Method, Import clones separately ROM location, set the destination folder to any valid folder. Doesn't matter. Import the 'games' Now open the Filter Arcade Platform feature Select the new platform (MAMEchds) and filter out, delete the excess junk. See what's all left.
  23. "Were there's a will, there's a way". I can add it to the "to-do list". What exactly would you like to see in your text file? A comma delimited format with all data ROM,Title,Parent (aka clone-of),Status (useful for importing into a spreadsheet) Just the Rom, Title In the meantime you can: At the top of that plugin feature's page click See all these on the Arcade Database To remove Software List CHD's Check the box MAME Cab Only then click Search To filter out clones (see Parents only) un-check the box Show Clones then click Search To see only one with a status of "Good" Click Additional Filters in the Emulation dropdown box, select Working then click Search Once satisfied with your filters Click Options Click Export the Results Change the Title to something meaningful to you Click Text (txt) (other output formats are available and may supply more datum) Click Export The saved file will look something like this MAMEcabOnly-noClones-Working.txt (BTW, the txt file output I'd create would not be column formatted like ADB's output shown above)
  24. First off, thank you for your patience. If there isn't a specific platform available on the LaunchBox Games Database site for this, you can submit a Feature Request to have it added. Go here Feedback - LaunchBox Games Database and click Create A New Post. You can also, near the top of this page click the Downloads 'tab' (scroll to the top, it's located between the Activity and Gallery tabs. Not the 'Download' button at the very, very top). Click Submit a file. If you can't find an appropriate category to select, at the very bottom of the list is LaunchBox/Big Box Media.
  25. Thanks! I appreciate that. MAME is unique to any other emulator. I don't think there'll ever be a one-click option for that. Providing a means of obtaining ROMs is not an accepted practice of LaunchBox. Plugin or otherwise. Providing a means of updating the MAME emulator alone lends towards massive volatility. e.g. The end user doesn't update their ROMs, but "we" update your emulator, you're looking at possible compatibility issues. Sometimes old ROMs work with newer MAME emulator revisions. Sometimes they don't. No one want's to be set up for failure.
×
×
  • Create New...