JoeViking245

For this, you'd need to create a plugin (written on C#). Essentially, it'd catch a selection change event, determine that the change went into a playlist (vs say a different game, a platform or a platform category) and that the playlist is 'your special playlist'. From there, execute what you wanted done.

I do have a cab, but set the controls up for the emulators I use several years ago. For any newer emulators installed since then would be for 'newer' systems/consoles which work best with a controller. I use an Xbox 360 wireless controller for those. You really shouldn't be having any input conflicts. After a game is launched, LaunchBox/BigBox "takes a backseat" with its mapped inputs (keyboard and/or controller) except for, of course Pause and Exit [the game]. There are some 'specialty' inputs you may have mapped that will still be available as well, such as screen capture. Aside from those, after launch, it's up to the emulator and how you have them mapped in there. Typically, with the default mappings for a keyboard encoder in a cab, you shouldn't need to change anything in MAME [from its default mappings]. Which I think you already found is the case. And actually, don't ever change the mappings for the encoder. Change them in the application-specific mappings. Generally, RetroArch's default mappings will give you a real good start. But for some systems you may want to change things around. Myself, I didn't have a lot of time on the NES system growing up. So playing that on my cab, to me, the A and B buttons seem backwards. So I changed those for that system. Regarding these RA (RetroArch) issues, it sounds like you've done some remapping in RA. None of those 3 should be mapped to any of the [regular] player buttons/joys. (or player button-combos). You need to break it down and figure out which button presses exactly (in RA) are causing those. i.e. if Player-2 presses their Button-4, the game pauses. Then find out if it's like that for all Systems you play in RA (i.e. it does in NES and SNES). Or if it's just in one of the Systems it does that. In this example, you then look in RA's default settings for what's assigned to "Pause". If it set to "w" (aka P2 Button4), then you know the issue. To find out what 'letters' are assigned to which buttons on your cab, open Notepad and start pressing the buttons. i.e. Press Player-2, Button-4 and a "w" should appear. As for how to map the buttons in RA (general or System or game specific), there are many threads already covering that, I'm sure. But you need to have a basis for what's-doing-what wrong before you can fix it. Then once you've at least attempted to research how to setup or change this-that-or-the-other-thing, then ask. Be sure to specific give details.

In your Flycast emulator folder, edit emu.cfg and set fullscreen to yes. [window] fullscreen = yes In LaunchBox, edit your Flycast emulator. In the Running Script put: $Esc:: { WinClose, ahk_exe {{{StartupEXE}}} }

The keyboard mappings in BigBox are separate from the mappings in MAME are separate from the mappings in RetroArch are separate from the mappings [insert any other emulator here]. Note, the mappings are also separate between LaunchBox and BigBox. That is, your cab, using keyboard input(s) will work in BigBox and most any emulator. However, you need to set the bindings up separately for each emulator. Fortunately, though RetroArch can emulate many systems, it's considered one "emulator" (but not technically an "Emulator" in itself [by name]). So that will save some time.

Without making attempts to fire this system up myself, when you run the system in MAME itself, are you able to load the cassettes there (along with ExelBASIC)? If not, any further consideration is a moot point. What softlist cassettes are you using? (I didn't see any that were associated with the system.) Your command line loads the exl100 system and then attempts to load the [non-existent] cart exl100. Probably remove that part (-cart exl100). To add a literal " (quote) inside the command line, I believe you just need to double it. load""1"" You can't switch the ui_active mode (keyboard mode) from within an autoboot script to be able to press keyboard Esc and then UI F2 (play). But I'm sure you can accomplish that via a LUA script. This guy's made quite a few, though not one the EXL 100. But you could use one of them as an example and modify it for exl100. https://github.com/Bob-Z/RandoMame/tree/main/autoboot_script To find what keys are assigned for Shift and Esc on that system, [you might be able to] start it then go into the Tab menu and look at what's assigned there. Looking at your original how-to, you have in there ((ENTER)) and ((F2)) which appear to be literal keys. Whereas ESC is not inside double parenthesis which would lead me to believe it's the 3 individual letter keys. Maybe it's just semantics. But in print, they appear different. To me, all this seems like a lot of work for a system that's marked as Preliminary and only has 16 carts (plus however many cassettes you may have come across). But that's just me.

dash autoboot_command (no space between) -autoboot_command

Excluding items from All would make All not really All. I have several [non-]games similar to the examples you listed in several of my builds. They're in their own Platforms. So not intrusive to anything else. Personally, I don't think I ever really click on All to look at/for games. But I do have it Enabled to show. However, since it's enabled by default, I'm sure a lot of people do use it. A possible option you could do is to rename All (in Tools-Options) to something like Everything. Then create a new playlist and call it 'All'. In the playlist, you'd have it exclude the items you don't want to see. i.e. ROM Path - Doesn't Contain - Http The problem with this is the playlist needs to get populated whenever you load it. Depending on how many [actual] games you have in your collection, that could be time consuming. (Minor. But still a factor.) All, as it stands, is just that. It has no filters to cross-check against, so it can just grab your entire collection without prejudice. My opinion, All should be All. Without bias. Non-games should be in their own platform and can be restricted as such (i.e. switch to Platform Category view and have the non-game platforms not have any "Parents" checkboxes checked.)

I presume those folder names look similar to Platform names. (That, or exactly like platform names.) They're auto created when you have auto import enabled. (For games. Not to confused with the auto import for storefronts.) This allows you the proper folder names to drop your ROMs into to have LaunchBox import them from.

Yeah, that'd require a plugin to capture the controller input. Then you'd navigate away from BigBox. And then you have to grab your mouse and keyboard to continue navigation in wherever the link sent you. Since you have to grab the mouse anyway, may as well grab it early and right-click the link in BB. (Assuming the mouse right-click capture works in BB.)

Glad to hear after almost 2 years later someone actually tried this and it working! Never thought to try it in BigBox. TBH, don't think I've ever used a mouse in BB. Keyboard navigation (cab buttons), yeah. Controller, of course.

Not to infer one way or the other, but Custom Icons does require LaunchBox Premium for them to show.

I don't know about TeknoParrot, but here's a tutorial for setting Hypseus Singe in LaunchBox.

Since it's all working, are you just wanting to hide the console window?

14? Really? Anyway, I think you'd be better off with an inexpensive mouse. Definitely don't need anything fancy. A wheel mouse would be ideal. Being wireless has it benefits.

I don't know if it's the way to do links. But it is a way. I just tested my old theme in which I had experimented on (a copy of Default Plus), and it still works. Which leads me to believe there's no reason it won't work on others themes as well.

The keyboard shortcuts listed in that link are for their "LaunchBox" (referred to as "the LaunchBox"). Not to be confused with (this) Unbroken Software's LaunchBox. You can Tab through the panes and then arrow Up/Down in the respective panes. Still, it's pretty 'clunky' that way as [the Real LaunchBox] it's meant to be a Windows based keyboard and mouse application.

Or if you're feeling adventurous, you can get MAME to do it (almost) all for you via lua scripts.

Right-click the file and send it to the Task Bar.

Couldn't see which file it was. If you can find an old enough backup that's not too old and is a valid xml file, use it. (or) with LaunchBox not running [and properly, completely shut down] delete that file and start LaunchBox. It'll recreate it. You may need to make some adjustments to get back to where you want it.

As it states, the xml file is corrupted and missing the root element. As it's happened twice (so far?) on only one of your 10 PCs, my guess is that LaunchBox is not being shut down properly. That, or it's being closed properly but the computer is being powered off right away or if on a portable drive, being unplugged right away. a.k.a. LaunchBox closes [visually] but it's not being given time to write/save to the xml(s) in the background.

I personally don't have Xbox Game Pass, but here's a video tutorial on importing them. It's a couple years old, so hopefully it's still relevant. If not, please report back and hopefully someone will chime in.

That is correct.