JoeViking245

No. You can remove the "OLD square corner". You just won't be able to use that [customized] theme. Again, you need to purchase a license to be able to use a custom theme. You can't modify the Default Theme because it will "fix" itself if changed. (hence needing to make a copy). As all was stated previously by Neil. You could try the Old Default theme (which I believe still comes with the free version) and see if that's better suited to your liking.

You can practice it in theory by following along in the above posts. Main key point is, if using the Default theme, you need to make a copy of its folder and then edit the copy. That said, the free version of LaunchBox does not support custom themes. So to make the above 'practice' a reality, you would need to purchase a license.

When it does freeze, if you press Alt+Tab and (while holding Alt) tab to Big Box, let go of Alt, does it then function as it should? If so, check your Keyboard Mappings to see if you have Esc mapped to more that item. Be sure to check in Keyboard Automation also.

If you indeed have a non-merged set (and not a merged set), you could use Tools - Scan - Scan for Removed ROMs. That'll bring up a message box with "the list". You can then highlight and copy the contents of that message box to a text file. Or wherever. But it's limited to showing only a certain amount. So if you have a ton of ROMs missing, you may need to do it in stages. And there it is. Also, MAME rarely changes ROM names. And usually when they do, it's actually a re-naming of a ROM. i.e. the game 1942 (1942.zip) When they had the Revision A ROM, it was named 1942.zip. Then when they came across Revision B, 1942.zip became 1942a.zip, and Rev. B became 1942.zip. With certain disorders comes great personal responsibility. If the Scan mentioned above doesn't fill the void enough, you may want to Request a Feature. (Top if this page under Help & Support)

I think 32X may also need 32x.zip. (It's been a while since I looked at it.) Start with checking both boxes, just like you do with Arcade. (In fact, you could just the one emulator. Up to you.) Then in the Associated Platform section, add to the beginning of the command-line parameters -rompath %romlocation%. This assumes any BIOS or other support files for that console are in with the console's ROMs. (as you indicated you did with SNK) See if that helps any.

Could it be you have Exit Game mapped in LaunchBox? (Tools < Options < GameControllers < Mappings) Or if in Big Box, Close the Active Window. (System Menu < Options < Controller Mappings)

K. Just wanted to clarify the actual message.

Umm... Sound precarious. Can you share a screenshot of that actual message?

Are you able to run games directly from stand-alone "Retro station" (or did you mean RetroArch?)? That is, without trying to launch them via LaunchBox.

Get creative and have the batch file "tell itself to run the commands elevated". You don't need to run/execute this [example] batch file as Admin, but it will start "notepad.exe" elevated (as Admin). Adjust ONLY THE ONE LINE to meet your needs, accordingly. @if (0)==(0) echo off >nul 2>&1 "%__APPDIR__%net.exe" session &&goto __elevated__ set __args__=%* "%__APPDIR__%cscript.exe" //nologo //e:jscript "%~fs0" exit /b :__elevated__ :::::::: update below here ONLY :::::::: start "" notepad.exe :::::::: update above here ONLY :::::::: goto :eof @end new ActiveXObject('Shell.Application').ShellExecute('cmd.exe','/c ""'+WScript.ScriptFullName+'" '+new ActiveXObject('WScript.Shell').Environment('PROCESS')('__args__')+'"','','runas',1); Don't change anything except the line that starts with start. Change that line to execute whatever you need ran as Admin. Pro tip: Lines starting with :: (2 or more consecutive colons) are comments in a batch file. Alternately, you can add comments by starting the line with rem (short for "remark") and is not case seNSitiVe.

The LaunchBox Games Database is user supported. Forum support for the database is located here: LaunchBox Games Database - LaunchBox Community Forums Being as it is user supported; you can add it to the database by going here: LaunchBox Games Database and click on Add new Game.

If that' the case (it works in MAME stand-alone) then remove -rompath %romlocation% from the Default Command-line Parameters.

Again, it scans the imported games you have and "verifies" each games' path_to_the_file. Chances are, you have a ton of games in your Arcade platform and you may never come across [to play] the missing ones. Going back to your original post... do you mean non-merged set? Because as stated, a merged set will create the issue you're seeing with "missing ROMs". Which really, isn't an "issue" with a merged set. Think of it as a false-positive. At this point, with your ROMs in their new location/drive, you could remove your existing platform then do a 'fresh' import on the ROMs [from the new location]. Combining the clones in with the parent ROMs as additional apps if you wish.

It's the Additional Apps that get ignored. If you combined your ROMs during import, then the clones (depending on your region priorities) are what's in the Additional Apps. I can see this happening with a merged. But you indicated you have a non-merged set. Have to ask, are you positive it's a non-merged set [and not a merged set]? Did you check any of those 12 to see if they actually don't (or do still) launch? MAME ROMs in LaunchBox are handled a little differently than conventional ROMs. Especially with the possibility of users having non-merged, merged, or even split sets. With merged sets, the clone ROM files don't physically exist. This is why you can't (or rather, shouldn't) use Scan for Removed ROMs. Well, it looks at the path_to_the_ROM. Then it checks if that file physically exists. I'd verify that those 12 indicated games do indeed not launch. When (if) moving your MAME ROMs and using the File Management feature to reassign their location, they should still work. And the missing ROMs (in the case of MAME) may be misleading.

The error indicates something is up with your license file. Email support@unbrokensoftware.com and they can sort it out for you. Anytime an error code like that is tossed it's one of three situations: 1. The license is banned 2. The license has been altered (you tried to change details in the file, or the file has been corrupted). 3. You are using an Android license on PC or vice versa

Not that I've seen. You can have custom Startup screens per platform within your selected Startup Theme. But not for Shutdown screens. You can however customize the Shutdown screen (change it up to your liking) in your selected Theme. But is still a one-Shutdown-screen for all platforms.

To better help you, can you please share some screenshots of how it's setup in LaunchBox? Edit your MAME emulator and show screenshots of - the Main Details section - the Associated Platforms section Edit one of your Arcade games and show screenshots of - the main Metadata section - the Launching section - the Emulation section

"no longer work" is pretty vague and open ended. To help the plugin developer resolve your issue, you need to provide [at least] a little more detail. i.e. Is there an error message of any type? Can you see it in the Tools menu and then click it to open up settings? Again, those are just examples. The more details you can provide, the better chance there is at actually resolving your issue.

It's because in v1 you could set the index. Which really shouldn't be done. That's why Jayjay removed it in v2.

This plugin was written about 5 years ago. It will not work with current version of LaunchBox. (would need v13.18 or older) If you're using RPCS3, LaunchBox v13.15 (July 2024) added a new feature making this plugin unnecessary.

It looks like you created your plugin using version 1 of the app. Try using version 2 (at the top of the page in the link). Custom Badges - Third-Party Applications and Plugins (Development and Beta Testing) - LaunchBox Community Forums

Though we can appreciate your enthusiasm and concerns, please don't post the same issue in multiple threads. I removed your other post. We can continue discussions here (in 1 location). Can you attach one of your custom badges dll files that appears to be causing the issue you described so it can be looked at tested?