JoeViking245

Quite a bit of work? @jayjay already took care of the hard part. With his app, my guess is 5 minutes tops. The app to create the Custom Badges was created almost 5 years ago. That was when LaunchBox was still on .NET Framework 4.8 (even before "upgrading" to .NET Core 3.1, .NET 6 and now .NET 9). I, JoeViking245 promise you it still works. And the resulting Badge plugins will continue to work. Then once when you create the resulting .dll file, you can become a hero and share it with the Community for others to revel in your hard work. Plan "B": Request a Feature. Feedback - LaunchBox

I think your best (only?) option in this scenario is to create a Custom Badge.

If, when you launch a game in Xemu or Supermodel and you get the black screen, at that point, can you hit "the hotkey(s?)" to disable HDR and it fixes it? Or.... do you have to hit the hotkey to disable it BEFORE the emulator is loaded? What exactly is (are?) the hotkey(s) used to disable/enable the HDR? These will determine where and how to best accomplish this.

Yeah, that is just crazy. As a "standard of the industry", for keyboard input, P1 - 2 and 3 should be Alt and Space. At least that's I-Pac default as well as MAME. Making it pretty much plug-and-play. Heck, I bet even by default, that's what RetroArch would expect. But none of this helps you. Unless that's some sort of XInput thing (my I-Pac doesn't have XInput capabilities, so I wouldn't know). I'd be incline to call the cab manufacturer (I assume they pre-setup the encoder and emulators etc.) and ask them what they think. Maybe even tell them to fix it. Because I'm sort of doubting you're going to be able to get the [brackets] to work in Supermodel. Play B would be to reset the I-Pac to default and remap the emulators 'properly'. (just my opinion)

My guess is that it's not freezing. It's just [ (bracket) is not a valid input [for Supermodel]. Curious, which buttons are assigned to the brackets? Like Player 3 - Button 7 and Player 3 - Button 8?

Top of this page: Download. https://www.launchbox-app.com/download

An issue with incompatible plugins was fixed in release v13.20. May try updating to that version.

It doesn't help [me] since I don't own one. When you say "mapped as 1 & 5", I assume you mean 'keyboard' 1 and 5 (vs a 'controller button' 1 and 5). It's been a while since I did much scripting and forgot MAME needs a key delay. SetKeyDelay, 0, 50 1 & 5:: Send {Esc} Return 1::1

Here, you'll need to press [and hold] "1" FIRST, then press "5". 1 & 5:: Send {Esc} Return 1::1

As just a guess, I suspect this 'alphanumeric ID' is in the format of a GUID number and that this GUID is the same GUID as the game in question. The filename (GUID) may also end with -01 (or similar). I further speculate that at some point between clicking OK to save the changes you made for that game and closing LaunchBox (allowing it to finalize saving any remaining changes in the background) that the 'placeholder' file will be removed. But it's just a guess.

What you're seeing is actually an empty 3D Model (vs a 3D Image). The Models get composed from Box-Front, Box-Back and Spine (or Clear Logo) images. They actually look quite nice if you have those images available. You can disable the "hideous" 3D Model image under Tools < Options < Visuals < Game Details - Show 3D Model.

In LaunchBox, edit your MAME emulator. In the Default Command-line Parameters, remove -nofilter. Edit: Apologies. It's -artwork_crop that needs removed.

As a workaround (though not ideal), you can edit the individual Additional Apps and manually set them to do what you want. Uncheck Use Emulator then add the path to MAME and the appropriate parameters (including the ROM name).

I think what you're wanting to do is, using the same particular ROM (i.e. aof2.zip), have multiple "copies" of that ROM imported into LaunchBox, but each "copy" loads using a different BIOS. It'll of course be the same physical file (aof2.zip), but seen 3 times. i.e. aof2 (Jap BIOS) aof2 (Eu BIOS) aof2 (US BIOS) How you'd accomplish this from the command line is to add the parameter i.e. -bios 16. ("16" being the variable/number of the BIOS for that game as MAME sees it). Unfortunately, this isn't possible for Additional Apps ('Alternate Versions') because you can't add Custom Command Line Parameters to them.

I just ran a test to confirm what you're experiencing. Tools < Import < ROM Files < Single Platform In my case I selected a folder "Nintendo 64". It auto-detected the platform and then gave the option to install RetroArch. Choosing "Install RetroArch", the wizard proceeds without giving the option to download bezels. Test #2, same steps but instead of having LaunchBox automatically install the emulator, I selected "Manually Configure Emulator". Added a new emulator (RetroArch) and continuing through the wizard, the "Download Bezels from The Bezel Project?" screen appeared this time. My guess as to what's happening is, when choosing "Install RetroArch", RetroArch isn't technically installed until the end of the Import process. So the wizard doesn't "see" retroarch,.exe and skips the bezel section. The good thing is, it'll only do that once. Or at least until RetroArch exists as an emulator. The bad thing is it happens once. The easy fix is to re-add those games and the wizard this time should show the bezel option screen. Subsequent platforms using RetroArch as the emulator should see the bezel option screen during the import wizard as well. Feel free to report a bug here: Feedback - LaunchBox This way the developers will have a 1st hand report of the bug and can process accordingly. (Rather than them sifting through oodles of Forum threads.)

Select the games in the given platform and then go to: Tools < File Management < Change ROMs Folder Path for Selected Games...

Looking at \LaunchBox\Themes\Documentation.pdf, it'd be ActiveGame.BannerImagePath. (or maybe ActivePlatform.BannerImagePath)

The reason I asked which emulator you are selecting to use is, I believe the "Download Bezels from The Bezel Project?" part of the Import Wizard only appears when selecting RetroArch or MAME as your emulator. I also believe the wizard looks at the actual executable filename (vs the name/title you gave the emulator). So, "retroarch.exe" and "mame.exe". I don't know if it looks for forks of MAME like "mameui.exe".

Looking through in your previous posts, I still haven't seen any actual script. Maybe when you're at your computer, you can take a moment and share what you actually have there. Unless what you're saying is that your Running Script actually consists of just yo. And nothing else. Then of course it's going to error. Not sure where you'd get that yo is actually a command of sorts.

The Additional Apps look fine. What happens if you remove the erroneous script from the Running Script section? What is the Running Script you have supposed to do? Why is it erroring? What's the action it's not recognizing? What does the whole script look like? It's not supposed to start JoyToKey is it? If so, why are you starting it twice (via the Running script AND Additional App)? If you fix the error in the script, can you remove the Additional App? Sorry so many questions. My mind reading skills have been on the fritz lately.

I've never done the download bezels feature so I won't be able to help you. But for someone who might be able to help you, what you're missing could possibly be providing some details on how you're going about doing what you're trying to do. How are you importing the games? Tools Menu? Drag & Drop? A group (or folder) of files? Just one file at a time? Letting the Auto Import feature do its thing? What emulator are you selecting as the emulator? MAME? RetroArch? Dolphin? Xemu?

All scripts aside, you say you have JoyToKey set as an Additional App. Is it set to Run Before Main Application? Can you share a screenshot of this Additional App? And when you launch a game that has this Additional App set to Run Before Main Application, the game launches minimized? BUT, if you remove the Additional App, the game launches fullscreen? That doesn't make sense. Now back to scripts... Your script that's giving you an error message, "but it works", where/how exactly are you running this script? As an Additional App? In the Running Script section of the emulator? Are you running it as well as the above Additional App? Or just the script? When you say "it works", are you saying it launches JoyToKey and the Dice game opens fullscreen? What is the error message? What does the script look like? If you click OK on the error message, does it go away and "everything works"? With as much information you've given us, you really haven't given us anything to be able to help you.

My guess is that you have 'Attempt to hide console window on startup/shutdown' checked. Do you have Dice set to start fullscreen? Whether you run a batch file or an AHK script shouldn't matter. They're essentially the same thing. How are you running them "at the same time"? When running your batch file (or script) and Dice outside of LaunchBox, do they 'play nice" with each other? Have you tried running JoyToKey as an Additional App to the games and set it to Run Before Main Application? You should be able to run that directly without the need of a batch file or script.

You were on the right track. You'll need to edit the specific game in LaunchBox and use game specific custom command line parameters. In 'what you tried' #4, what you're looking for is -cfg_directory. This thread shows it being used for the NES softlist.

Command line: --fullscreen=true Or you can edit xenia.config.toml [Display] fullscreen = true