JoeViking245

Aw snap! That what happens when I try to clean up my working code. 😊 I'll fix that post for future readers. Glad it all worked as intended. Sorry the outcome wasn't as hoped. 👍 👍

Fear not. If you can get the paths and executables, it will. 😎 (I actually tested this one before posting. Something I'm trying to get better at actually doing. lol)

No need to. Just create the batch file and use it to start LaunchBox. It'll do it all for you. A one-shop-stop, as it were. (You could even to change the icon for the shortcut to use the one in LaunchBox.exe. )

If, when you disable G-Drive syncing and you're happy with how LaunchBox/BigBox performs via G-Drive (which I guess at this point is actually running from your local G-Drive folder), then... A variation of a Google search result looks like this: This link mentions "googledrivesync.exe" which is now "GoogleDriveFS.exe" (at least on my PC). It seems there's no command-line parameters you can pass to the executable to turn G-Drive syncing on/off. So you have to "kill" the process. From the Windows Command Prompt, to kill G-Drive altogether, you can run taskkill /IM GoogleDriveFS.exe /F Then to restart it, double click "GoogleDriveFS.exe". Mine's located in "C:\Program Files\Google\Drive File Stream\100.0.2.0\" LaunchBox/BigBox has a Startup Applications feature that can load an application when one or the other or both (or neither?) are started. (Which could be a batch file containing the above command.) But there are no (immediately accessible) means to launch an app when either close. "Immediately accessible" meaning, you could create a plugin that captures the System Event LaunchBoxShutdownBeginning and/or BigBoxShutdownBeginning and then (re)start the process "GoogleDriveFS.exe". Alternately, you could create/use a batch file that handles the whole kit-and-caboodle. Something like this (edit accordingly) taskkill /F /IM GoogleDriveFS.exe timeout 5 start /w "" "D:\LaunchBox\Core\LaunchBox.exe" start "" "C:\Program Files\Google\Drive File Stream\100.0.2.0\GoogleDriveFS.exe" Do This: Verify YOUR Google Drive executable is indeed "GoogleDriveFS.exe" Change the path to YOUR LaunchBox location DO point to the /LaunchBox/Core subfolder Change LaunchBox.exe to BigBox.exe if that is your preference Verify that is the path to YOUR "GoogleDriveFS.exe" If all's good/tested/working, make for a 'prettier' presentation... Create a shortcut to the batch file Right-click the shortcut and select Properties Change Run from Normal Window to Minimized Click OK to save and close. Use the shortcut to start the "whole kit-and-caboodle". The above makes it so the Command Prompt window does not appear.

This would be located in your Windows "Display Settings" under "Scale and layout".

Take a look at this and see if it helps.

The only times I've seen this happen is when I launch the game, and it's the 1st time Steam has been launched (on that particular day), and Steam has an update. Steam will do its update thing and then show the "On Sale" and 'Main' windows. This happens in the background, so you don't see anything when the game [eventually] starts, and you play it. It's when you exit the game you see those windows still lurking [on top of BigBox]. I've gotten in the habit of, before I start BigBox, if I know I'm going to be playing a Steam game, I'll Start Steam 1st. Let it do its thing close/minimize Steam when it's done then start BigBox.

Hopefully your ones with .iso and the ones with .cue/.bin are for different games. That is, if you have all 3 in one folder (for one game), you essentially have 2 copies of the game. Either way, if you have them all imported into LaunchBox already, there's a plugin for that. Well, not sure about .wav files. Haven't seen those before. At least not in this type of scenario. I'm sure there's a ton of them. Could probably search for "chdman convert iso to chd" or "chdman convert cue to chd". Key term being "chdman". Might even find something for "chdman convert wav to chd" if that's actually a thing. (Again, outside of my knowledgebase)

Pretty sure the marquee image being displayed does not distinguish between "perusing through your platforms/games" and "playing a game". That is, when looking at a game vs playing the game is the same thing (marquee image-wise). I assume you have game-specific marquee images because when you're scrolling through your games, that's what you'd like to see. To have that image change when you go to play that game seems counter intuitive (to me). You might try looking into using the ThridScreen plugin. I don't know if it will distinguish between the 2 scenarios you want, or not. But it's pretty feature-rich and if nothing else, it may have a feature for manipulating the image type used that'd work for you.

You hit submit reply before I finished typing. lol Glad you got it working.

You called the emulator Arcade, which led LaunchBox to believe it was going to be MAME. So it auto-filled the command-line parameters and had 2 boxes checked. You un-checked "Remove file extension...", but you need to also un-check "Remove quotes" like in you first post. The default command-line parameters that were auto-populated (for MAME) are incorrect for RetroArch. Delete that. Which brings us to the Associated Platforms section. You didn't assign the core to the platform. Your 2nd post indicates that it was, in your old install (because you at least got the FBNeo error message. That's just because it's just opening RetroArch. When you start a game directly from the RetroArch front-end, and you tell it (or just load) a FBNeo game, it knows what core it needs to load to make it work. So it does [work]. Because you didn't tell LaunchBox to tell RetroArch which core it needs to use.

From your 3rd screenshot above... Tools < Manage < Emulators - select RetroArch.

Music files (not to be confused with the audio you hear from videos that are playing) are only downloaded if; when in the Download Images/Media wizard, in the EmuMovies section, you have Music checked. The easiest way to remove the Music files that have been downloaded is to simply delete the Music folder. i.e. D:\LaunchBox\Music\ Note: When you go to restart LaunchBox, that folder will be re-created as well as [empty] subfolders named after your Platforms.

Yeah, RetroArch is pretty smart when running it from its UI. The error message you show is actually referring to your contra.zip ROM. Specifically, appears it can't find the ROM. Try un-checking "Remove file extension and folder path". This way it'll send the full path to where the actual ROM is located. Then in Associated Platforms, when you added "Arcade" (or whatever you decided to call the platform), make sure "Extract ROM" is un-checked.

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.