JoeViking245

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.