JoeViking245

It's possible because the version associated the above View Download is 4 and a half years old. You might try using a more current release.

Most likely because, although I frequently (well, monthly) update MAME, the updates don't update any of my cfg or ini files. I did see they changed their default Pause mapping (back in February I believe [0.263]) and my thought was... If it ain't broke, why change it.

My pause binding in MAME is set to "P". Not sure if that makes a difference. Here's my LB settings where the default Pause screen doesn't seem to have any issues:

It will only change the entries/parameters you have listed in the .reg file (like the example shown in my 1st response only has one entry). If you saved/backed-up the entire reg section, yes, it will adjust all the ones listed. Indirectly, yes. This is where we get 'creative'. There aren't any command-line parameters specifically for showwindmd (DMD/Display Window) or showpindmd (external DMD (dll)). But you can set/reset those in the tables script. (See When all else fails below) There're (up to 9) Custom Parameters you can pass to the tables script using -c1 [Value]. 'Value' is any word you want it to be, placed after -cx (where x is a number 1 thru 9). i.e. To pass the Value "joewashere" as parameter "1", your [LaunchBox] command-line parameters would be: -c1 joewashere -minimized -exit -play To get the parameters' Value from inside the script, use GetCustomParam(1) (where "1" is a number 1 thru 9, corresponding to the "x" in -cx) Star Trek: For this table, I don't think you need to change the 2 'show...dmd' registry entries. "I don’t understand why the internal DMD isn’t showing." The internal DMD for Star Trek is forced-hidden by default in the script. It uses the same variable as shown in my 2nd post, VarHidden. And is hardcoded to "1" (line 47). To override this variable, check for the Value of the parameter -c1, then reset the variable. (if the command-line parameters do not contain -c1 joewashere, this won't trigger nor error.) Alternately: (Because I always love to give options) You can simply change the "1" to a "0" on line 47 in a copy of the script. No command line parameters required. If VPX was setup correctly, you should be able to right-click the .vpx table (file) and select Extract VBS. Or from the Windows Command Prompt, you can run VPinballx.exe -ExtractVBS "Star Trek 25th Anniversary (Data East 1991).vpx" This will create a new file "Star Trek 25th Anniversary (Data East 1991).vbs". Edit that file (with any text editor), change the "1" to a "0", and save. If a vbs file named the exact same as the table exists in the same folder as the table, it will override the tables internal script. Rename the vbs file to something like "NO-Star Trek 25th Anniversary (Data East 1991).vbs" (anything that's not the exact same name as the table) if you wish the use the internal script. Rename it back to the same name as the table to override the internal script. This method is nice because you can change all sorts of stuff in the extracted script file, then just rename the file to use the original table-script. From here, you can create a batch file / AHK script / whatever, that when ran will rename the file with/without "NO-" at the beginning, before launching the table. So....: Look for the variable VarHidden in the script(s) and see what they're doing with it. Adjust accordingly. "VarHidden" is commonly used, but someone may use a different word for it. If you don't see that particular variable 'name', you can [usually] see what they used inside the sub routine Sub Table1_Init, for .hidden. (The routine may just be called Sub Table_Init [without the "1"].) Either way, all tables will have a something-something_Init When all else fails: If the above isn't working (i.e. Simpsons), and you do have to change showwindmd and/or showpindmd, you can add those into the above _Init routine. (Setting "True" or "False" to whatever they need to be.) This WILL change the Registry. So you'll want to change them back when exiting the table. Look for Sub Table1_exit() (or Sub Table_exit() [without the "1"]) and reset them. (Re-Setting "True" or "False" to whatever they need to be.) These MUST be placed BEFORE Controller.Stop! You can hard code this in the extracted script by removing the If line and End If. Again, with this method, no command-line parameters are required. But you DO still need the parts the "_exit()" sub routine. Note: this When all else fails section does the exact same thing as executing your .reg files. Provided the .reg files only contain the 2 entries.

Update... Looks like you may be able to a table override from the tables configuration file. Didn't test it. But looks feasible. If the table doesn't have a configuration file, just create a text file with the same name as the tables .vpx filename, and give it the file extension .ini

RE: for just the standalone version of Flycast, you state if you run it directly from the emulator, the game will load/play. But attempting to run/launch the same game via LaunchBox through the emulator, it won't start. So far, so good? What file format is the game you're [attempting to] run? If they're in something like .cue and .bin(s), make sure the game in LaunchBox is pointing to the .cue and not any of the .bin file(s). (An aside: CHD format is the cleanest, least convoluted format. It has the game in just a single file and will be a smaller physical size than the cue/bin(s) combined.) Situations that have been known to happen: (when all else appears correct) Any chance you have different copies of Flycast on your computer? As in... the flycast.exe you're testing with in stand-alone is a physically different flycast.exe than the one LaunchBox is pointing to? i.e. D:\Emulators\Flycast\flycast.exe VS D:\LaunchBox\Emulators\Flycast\flycast.exe Are you starting LaunchBox in Admin mode? Though this may appear to fix 'some things', it will break 'most other things'.

When you edit the table then open the Script Editor, you'll see something like If Table1.ShowDT = true then UseVPMColoredDMD = true VarHidden = 1 Else UseVPMColoredDMD = False VarHidden = 0 End If or Dim DesktopMode: DesktopMode = Table1.ShowDT .... .... If not DesktopMode then l23bg.visible=0 l36bg.visible=0 l48bg.visible=0 l67bg.visible=0 l71bg.visible=0 l72bg.visible=0 l82bg.visible=0 End If In the 2nd one, 123bg through 182bg are the elements that comprise the tables built-in DMD. (shown for reference) In either case (and those are just examples), you can force set the show-desktop("ShowDT")/desktop-mode to True. i.e. change to DesktopMode = True.

You can add a "Game" that's pretty much anything. i.e. Have a platform that's called Manuals. Add a "game" and have the Application Path point to a .pdf file. Then when you Play the 'game', it'll open the file in your system default PDF viewer. Same for .txt, .mp3 etc. If you have a specific MP3 player that's not set as your system (Windows) default, you can create an "Emulator" that it's Application Path points to it. Then for your .mp3 'games', in the Emulation section, use that 'emulator'. @Mad Panda's Soundtrack Player doesn't appear to be made for a direct launch. (But realize it was just an example)

Though the originating post is fairly old, I imagine at least some of it is still relevant. Your best option is to check with the emulators themselves as they may change over time. Not to be that guy who says to "just google it", but the easiest way I've found to research this info is to.. well, Google it. To find something more-so LaunchBox specific, I always preface the search with "LaunchBox". i.e. "LaunchBox Dolphin command line parameters". That's a pretty open-ended question, as it's different for each emulator. Many times, when you start the stand-alone emulator, it'll prompt you to and where-to place these files.

I imagine the BezelLauncher plugin would work with Vita3K and using these bezels.

Oh snap! I was thinking save states. For per game configurations, you'd use -cfg_directory " "D:\MAME\mame.exe" nes -cfg_directory "D:\MAME\cfg\nes\addfam" addfam Or nes -cfg_directory cfg\nes\%romfilename%

You'd need to add -statename to the command-line parameters. The full command would be: "D:\Mame\mame.exe" nes -statename nes/addfam -ui_active addfam Then in LaunchBox for your NES Associated Platform: nes -statename nes/%romfilename% -ui_active I add ui_active so the keyboard works normally. Alternately, you can set in mame.ini (or nes.ini).

Did you add it as you typed it? Or put a space after the f (as shown)? {dash}f{space}{dash}g

If you have the ROMs/games loaded into RPCS3 already, you can turn on the Auto-Import feature for the platform and LaunchBox will read RPCS3's virtual drive and import those games. So in this instance, no. It doesn't matter where you store them.

I can only [possibly] help with Visual Pinball. First thing is to make note of exactly which settings are changed and what those settings are for the 2 configurations, respectively. Next, find where those settings are saved to. VPX had started going to saving certain settings to .ini(?) files (haven't taken the time [yet] to fully look into it). These files can be per-table (which you don't need for what you're asking about) or global. Other settings are still saved to registry. Once you know the what's and where's, then you can start creating your scripts. One setting you'll need is for the ForceDisableB2S. Which (at least used to be [via old notes]) is located in the registry under [HKEY_CURRENT_USER\SOFTWARE\Visual Pinball\Controller]. To change that, (one way is to) create a .reg file (i.e. B2Son.reg) that contains: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Visual Pinball\Controller] "ForceDisableB2S"=dword:00000001 Create a 2nd file (i.e. B2Soff.reg) with the same text and change the last "1" to a "0". Then just double click one or the other of the files to change it. Once you've confirmed that works, then it's just a matter of transposing that into AHK (or batch file) lingo. Then there's the ScreenRes.txt file in which you set the screen number(s), screen positions etc. This [can be] a global settings file in which you could have 2 copies of (one for each configuration) and then your script could copy and rename for the one to be used/loaded. It's been a while since I messed with this, and it may even be an easier process. (i.e. command-line parameters to load certain configs?) But noting exactly what needs changed between the 2 (for your setup) needs to be spelled out 1st.

Do the games work when you start them directly from MAME itself?

Here's one for history.xml. Do not expect anything for mameinfo.dat. (at least not from me.)

MAME History.xml Viewer View File View game specific history from MAME's history.xml Inspired from MAME's built in feature in the main UI and via their in-game Tab menu Prerequisites Requires LaunchBox 13.3 or newer MAME or MAMEui set as the game(s) emulator "history.xml" (download it from https://www.arcade-history.com/) MAME users: Place the file in the "history" subfolder of your MAME emulator. i.e. D:\Emulators\MAME\history\history.xml MAMEui users: Place the file in the "dats" subfolder of your MAME emulator. i.e. D:\Emulators\MAMEui\dats\history.xml Currently only available in LaunchBox (not BigBox) Installing Download and then open the plugin file using 7zip. if you don't use 7zip, first unblock the file (Right click, select Properties, and click Unblock) then open it as you normally would. Extract the main folder from inside the zip file into ..\LaunchBox\Plugins\ i.e. D:\LaunchBox\Plugins\MAMEhistoryXml\ Start LaunchBox Using Right-click on a game and select View MAME History. Updating history.xml When loading the plugin, it will check your local version of history.xml against what's available on https://www.arcade-history.com/. If a newer version is available, you will be given the option to Update your local copy. Updating will attempt to download and then replace your existing file. As always, all thoughts, views, opinions, suggestions, comments and accolades are welcome. 😎 Submitter JoeViking245 Submitted 12/19/2024 Category Third-party Apps and Plugins  

No. Only if you're real lucky, copying the files will work. But don't do that. What was stated was "reinstalling LaunchBox over your existing installation"

When running LaunchBox-xx.xx-Setup.exe and setting the install location, the installer will add "LaunchBox" to the end of the location you chose. Just delete the trailing \LaunchBox before proceeding [when you see it doubled up]. And as you found/noted, you can't install it into a root Drive. No. Your saved data and imported games will remain when doing the update. Typically when this error occurs, it means that one of the program files somehow got corrupted. You can try reinstalling LaunchBox over your existing installation which will repair the file(s). Which you have done. So, this could indicate the ...Setup.exe file you have is corrupted. If you don't have a Premium license and you need the older version 13.11, contact support@unbrokensoftware.com and they should be able to help you with that. Worse case is there's something wrong with your license file. If you need to recover your license file, you can do so at https://www.launchbox-app.com/premium/lost-license.

Understood. But I'd rather not make any assumptions. That said... I assume that on this different PC, launching a game (just like you could on the 1st PC) "through Flycast directly, it works perfectly by opening the in-software game lists, then click on the game to open and play". If it does work that way, I'm not sure what to tell you. If it doesn't, then your issue is with the Flycast emulator.