JoeViking245

Running that command from the Windows Command Prompt from within the folder that contains mame.exe should create mame.ini. Then when you close the Command Prompt window and are back in Windows Explorer, the file should be right 'next' to mame.exe. If you don't have file extensions showing, the file type you're looking for is Configuration settings.

Along with your gamate game ROMs, do you have the gamate.zip system ROM? Same with V-Smile. You also need the vsmile.zip system Rom. Tomy Tutor needs the system ROM tutor.zip.

In LaunchBox, Edit the emulator in question (in your example, "Yuzu"). Tools - Manage - Emulators - select Yuzu and click Edit. Click on the Running Script section. Add in there: $Esc:: { WinClose, ahk_exe nameOfTheLosslessScalingProgram.exe WinClose, ahk_exe {{{StartupEXE}}} } Change "nameOfTheLosslessScalingProgram.exe" to the actual name of the executable you want to close.

Ya, like Neil says something's screwy with the command-line parameters. Should have been (with using the emulator installer plugin) -b -C Dolphin.Interface.ConfirmStop=False -C Dolphin.Display.Fullscreen=True -e Go into editing your Dolphin emulator and click Reinstall. See if that changes anything. My last-ditch effort process would be... Tools - Manage - Emulators Select Dolphin Click Delete ("are your sure"... Yes) Click Close Go to Windows Explorer and navigate to /LaunchBox/Emulators/ and delete the Dolphin folder Tools - Manage - Emulators Click Add For the Emulator Name, click the down arrow (far right) and select Dolphin from the pull-down menu Click Download "OK" "Close" Tools - Manage - Emulators Beyond that, no idea. Unless someone else knows what's going on, may have to wait until tomorrow when the developers are back online.

The Exit Script section for exiting from the Pause Menu. Only. You can try overriding the escape sequence by adding to the Running Script: (below your Run... line) $Esc:: { Send, {NumPadMult} WinClose, ahk_exe {{{StartupEXE}}} }

If you enter LaunchBox's Pause Menu and select Exit Game, does it work then?

Since you set your ROM paths in MAME, try removing from the command-line parameters -rompath %romlocation%

To verify, when you go to Tools - Manage - Plugins and select Dolphin, does it say it's on version 1.2? When you go to Tools - Manage - Emulators, do you have more than one 'Dolphin' emulator? What version of Dolphin does it say you have? (give it a couple seconds to do its version checks) Actually, this is probably when you see the popup errors. Close the message window(s). Select your Dolphin emulator and click edit. What does it show for the "Current Version"? Can you click Update? Click Update and let it do its thing. The current version should show as above. If it doesn't, click OK, then click Close to close Manage Emulators. Re-open Manage Emulators. Do the message window(s) still appear? Does it show Dolphins' version as 2407-68?

For issues related to your license please reach out to support@unbrokensoftware.com.

That error looks to be you're trying to load a table with a wrong version of the exe. i.e. a vpx table with a vpt (V9.0) version of the exe (Vpinball.exe). But you indicate in LaunchBox, the app path is pointing to the same exe that you can load a table from in stand-alone Visual Pinball via File - Open, Run. So not sure what's going on. Hopefully someone else can chime in with more insight.

Do other tables with a backglass work properly when launched from LaunchBox? Just not 24? When in Window's File Explorer, if you double-click 24.vpx, does it run properly [with the backglass]? (vs. opening VPX and then opening the table) In LaunchBox, when you edit your Visual Pinball X emulator (VPX), do you have the command-line parameters -minimized -exit -play ? Is the Application Path pointing to the x64 version of VPX? (assuming you may have the x86 and the x64 version of the exe)

That video was made many LaunchBox versions ago. You might be able to see that in "Old Default". Not sure if there's a Tools - Options menu item where that can be changed. You'd have to look.

Glad it was an easy fix. I don't know if you can edit the theme to have them show bigger. That'd be the only way (if even possible). Would probably be easier to use a different image. Generally, the less 'detailed' the image is, the better it appears. Less colors etc. And honestly, probably don't waste time attempting to make the one you have 'less detailed'. Just look for a different one.

Make sure the image file (Map.png) you use is good to use as a badge. Not sure what the criteria is, but to test you could take one of the existing (known good) badge images, copy and rename to 'Map.png'. (Re-)Start LB. Now see if 'that' image appears on a game that has a map. You may need to regenerate the dll using the new test image as I believe the image gets embedded into the dll, then extracted to the images folder when the plugin is ran. The Additional App one looks like it should work. The Custom Field one, as you describe and show above, won't. You say the Name and Value are "Map", but the plugin (screenshot) is looking for "Maps" (with an "s").

Sounds like what you want is a Custom Badge.

If you go into Tools - Manage - Plugins, does it show that the Dolphin plugin has an update? If so, update it (LaunchBox may need to restart) then try having LB install the emulator.

Thanks! 😁 Never used that one before. Might be good for the start of a new topic.

Tools - Manage - Emulators - Add Give it a unique name Point the Application Path to same as your other one is (mame.exe) Check those afore mentioned 2 boxes Switch to the Associate Platforms section and add Advanced Pico BEENA and check "default" Click OK to save.

You might try the wait parameter in conjunction with creating the shortcut. It (the 'screens') may be 'hanging up' on the Command Prompt window. Never looked into that emulator before. Probably best to start a new topic specific for it.

Typically when using MAME ROMs and adding the appropriate media option (i.e. -cart), they will work with having both those checkboxes un-checked. But for some reason with the Advanced Pico BEENA system, it does not. You could try a No-Intro set. But my guess is you'll have the same issue. I see 2 options to resolve this issue: Create a 2nd instance of MAME, in LaunchBox. You can point to the exact same exe. Just have this instance check those 2 boxes. Then use it for your Beena platform. This will only work with MAME ROMs (not No-Intro). Only use MAME ROMs with the MAME emulator (vs mixing in No-Intro sets) and have those 2 boxes checked. (I understand it's 'not an option' for you. But it's an option none-the-less. )

If you still want to make use of the startup/shutdown screens (which can be pretty cool), you can use the wait parameter (/w). To expand on the startup/shutdown screen issue, what's happening is when you launch the game (the batch file in your case), LaunchBox shows the startup screen. The batch file launches the [actual] game then closes itself (as in the batch file 'exits'). LaunchBox sees the 'game' that it launched (again, the batch file) exited, so then shows the shutdown screen. Adding the wait parameter causes the batch file to "hang around" until the [actual] game exits. When you exit the actual game, the batch file then closes/exits, then LaunchBox shows the shutdown screen. Having the batch file 'hang around' will not use up any notable resources nor cause any slowdown/lag/stuttering/etc. of the game play. And beauty is restored to your LaunchBox/gameplay experience. 😎

In Tools - Manage - Plugins, is the Dolphin plugin up-to-date (v1.2)?

I've always said the MAME UI. As in the MAME's user interface. It's less to type out. As a test, check the 2 boxes "Remove Quotes" and "Remove File Extension and Folder Path" then try launching a Benna game. This should just work based on the assumption you're using MAME ROMs and not anything like No-Intro ROMs. You didn't share the 3rd screenshot, so I wasn't sure.

The \LaunchBox\Core\Images\ folder is a symbolic link that only exists when LaunchBox/BigBox is running. The \LaunchBox\Images\Cache-BB\ folder (the one that's linked to when running) will change (update). If the purpose of your syncing is just to maintain a backup of your build, I'd exclude that cache folder (also the Cache-LB folder) from the sync operation. May look at setting up the sync software to only sync files that have changed. I.e. set it for 'update" rather than "mirror". That should save a significant amount of time.

Adapted from here, this MIGHT work. If nothing else, it gets you in the right direction of what you need to do. @if (@CodeSection == @Batch) @then @echo off set SendKeys=CScript //nologo //E:JScript "%~F0" start "" start.exe ping -n 2 -w 1 127.0.0.1 > NUL %SendKeys% "4" ping -n 2 -w 1 127.0.0.1 > NUL %SendKeys% "2" ping -n 2 -w 1 127.0.0.1 > NUL %SendKeys% "y" goto :EOF @end var WshShell = WScript.CreateObject("WScript.Shell"); WshShell.SendKeys(WScript.Arguments(0)); The 2 in "ping -n 2..." is a 2 second 'pause'. Adjust accordingly It may (or may not) be easier to do this using an AutoHotkey script.