JoeViking245

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.

That's how their UI works for software lists. I've never tried, while in-game pressing Tab and selecting a different game via their File Manager. That's a good 'Pro Tip'. Thanks! Can you edit your MAME emulator in LaunchBox and share a screenshot of: The main Details section The Associated Platforms section (where we can see your Sega Beena platform) (In LaunchBox) Edit one of the games [that worked for you when launched from the MAME UI] and share a screenshot of the: Launching section (Extracted from attached mame.ini for possible use with continued troubleshooting:) rompath "F:\Launchbox\Games\MAME;F:\Launchbox\Games\MAME Software List Roms;F:\Launchbox\Games\MAME CHDs;G:\MAME Software List CHDs"

Try adding start "" to the beginning. (And pretty sure remove the @ symbol also [for asterix.bat]) start "" ..\..\Emulators\hypseus\hypseus.exe singe vldp -framefile singe\asterix\asterix.txt -script singe\asterix\asterix.singe -sound_buffer 2048 -fullscreen -gamepad -scanlines -scanline_shunt 3 (in Cyber Shadow, add it in front of the last line... start "" "%emulator_path%".....) I assume since you have the full path to the emulator, the batch file is not located in the same folder as the emulator. That said you may need to switch to that folder, first. cd ..\..\Emulators\hypseus start "" ..\..\Emulators\hypseus\hypseus.exe singe vldp -framefile singe\asterix\asterix.txt -script singe\asterix\asterix.singe -sound_buffer 2048 -fullscreen -gamepad -scanlines -scanline_shunt 3 Then if you want to make use of LaunchBox's Startup and Shutdown screens for that game (have the Shutdown screen actually show after the game exits), add a wait parameter (/w) to the start line. (don't forget the "cd" line) start /w "" ..\..\Emulators\hypseus\hypseus.exe singe vldp -framefile singe\asterix\asterix.txt -script singe\asterix\asterix.singe -sound_buffer 2048 -fullscreen -gamepad -scanlines -scanline_shunt 3 You'll then need to do the above shortcut thing to hide the batch file command window. ...which now that I think about it, those screens may have been the issue. If you're so inclined, don't do anything I've said to do, above. Edit one of the games and turn off the Startup/Shutdown screens. Startup/Pause - check Override Default Start Screen Settings. Click OK to save and close. If that fixes it, you can then do the wait/shortcut thingy and re-enable the Startup screen (un-check override) [if you want to have them show].

Do the games launch when starting them directly from the MAME UI? Is the path to your sega_beena_cart folder in you mame.ini file? Or a better option, have the root folder that all your software list subfolders are in, in mame.ini. i.e. D:/LaunchBox/Emulators/MAME/roms/[all your arecade ROMs.zip] D:/LaunchBox/Emulators/MAME/roms/software/a2600/[*.zip] D:/LaunchBox/Emulators/MAME/roms/software/videopac/[*.zip] D:/LaunchBox/Emulators/MAME/roms/software/gx4000/[*.zip] D:/LaunchBox/Emulators/MAME/roms/software/sega_beena_cart/[*.zip] mame.ini rompath "roms;roms/software"

Can you share the contents of your batch file?

Haven't tested this myself, but since it worked for you from the command prompt (or maybe you tested via a batch file) without -cart, try removing that from the LaunchBox command-line parameters.

Well, "replace" depends on how you update them. Download the entire [new] set, delete the old one and put the new one in its place. Or download just the update set (way smaller download) and use something like clrmamepro to 'fix' the old (existing) set with the update set. THEN have LaunchBox update the emulator. You don't get any of the 'now playable' or 'new working clones' etc. added to your LB collection this way. But those 1 or 2 (more or less) are easy enough to manually add.

I'd be inclined to just update your ROM set and then edit your emulator in LaunchBox and have it Update the emulator and call it a day. I haven't read the entire whatsnew.txt file but (for me at least, so far) there wasn't anything of note that I need to add and didn't see any filename changes.

If the games Application Path is pointing to the batch file and not using an Emulator (vs the game uses an Emulator whose executable is the batch file), you should be able to remedy this by doing the following: In Windows Explorer, create a shortcut to the batch file [in the same folder as the original .bat] Right-click the shortcut Select Properties In the Shortcut Tab, change Run from Normal Window to Minimized Click OK to save and close Set your games Application Path to point to the shortcut (instead of the batch file) Click OK to save and close Launch the game and see if that resolved the issue.

Are you starting LaunchBox using the executable that's on the removable drive? The error (at least on the portion you shared) indicates it's looking for a file in /LaunchBox/ on the C drive. I'm guessing your removable drive is something other than C.

Hmmm. I didn't get any prompts. Not sure what else to tell you. Hopefully someone who's actually set it up in LaunchBox and use a controller with it can chime in and help.

That was many years ago and I don't have it installed anymore. And when I did, I never even fathomed to use a controller with it. Always just used keyboard and mouse. With as long ago as it was, I wonder if it could have even worked with a controller. lol That said, I just installed it (took forever) and did some testing. Try pressing Start THEN Back. 😊 I didn't get into the MultiInstance and HD-Player things. but found that the main app is BlueStacks X.exe. But killing that, it still runs in the toolbar/background. So then I found BlueStacksServices.exe. Added these to the 'list to kill'. This should shut it completely down. 1Joy7:: { If GetKeyState("Joy8") { Run, taskkill /f /im HD-MultiInstanceManager.exe Run, taskkill /f /im HD-Player.exe Run, taskkill /f /im "Bluestacks X.exe" Run, taskkill /f /im BlueStacksServices.exe } }

To use a button combo in an AHK script, try this: 1Joy7:: { If GetKeyState("Joy8") { Run, taskkill /f /im HD-MultiInstanceManager.exe Run, taskkill /f /im HD-Player.exe } } Press and hold 'Back' (Joy8) then then 'Start' (Joy7). My Xbox controller doesn't have button labeled "Select", so change "Joy8" to suit your needs. Place this in your Running Script section for the emulator. I haven't looked at BlueStacks in quite a few years. So the potential caveat here is, this will only work if one of those 2 exe's you're killing is the actual exe that's in the emulators Application Path you're initially launching.