JoeViking245

You're welcome. Great theory. However the Importer really doesn't care about you romset. Well, I suppose it does if you ask it to copy your ROMs into a different folder. But even then, it goes through the list (your above left photo) and attempts to copy the Rom (column 1) from the source to the destination folder you supply. And then I believe, if it doesn't exist (say in the case of a clone in a merged set), it simply moves on to the next file. If you are doing an Import Only (aka, phase 2 of Copy and Import), the plugin won't care if the ROMs exist or not. It just needs to know the path to where they're 'supposed to be'. No. It's the plugin. I personally never import clones as addition apps. Well, I never import clones at all for that matter. lol At least not in bulk. I've found it easier to add a few good ones, 1-by-1 then to remove a bunch of crap. Anyway, I had in the back of head that the Import as Additional Apps wasn't 100% and that I was "going to fix it later". And I did. Back in January. But appears I didn't share it. Thank you for the reminder. 😊 I'll update the original post with version "beta-04. "

Great catch! Totally forgot about the closing part of the element.

That's the old MAME format. BUT you might be able to open it in a text editor and do a find and replace [all]. Replace "<game" (without quotes) with "<machine" (again, without quotes). Be sure to include the less-than symbol (<), otherwise something like 88games will become 88machines.

If you have an xml file that's formatted the same as MAME does its Arcade xml files, there's a plugin that can help with that. But the xml DOES have to formatted the same way.

To view "Command", select External DAT View. Command Tab will only appear for games that are listed in command.dat. Mortal Kombat (mk.zip) is a good one to test with. You don't need anything special to view this. The paths should be setup by default. You just need command.dat in the dat folder. Again, this is for (at least) standalone MAME. I've never used RA MAME.

lol. Yes. What's needing to be done beforehand is to test everything in PCSX2 itself. Once that proves good, then move on to setting it up in LB Here's what I did: Had "-batch" (without quotes) as the ONLY command-line parameter in LB. Checked Start Fullscreen via the PCSX2 GUI. Removed all the old custom command-line parameters for every game in LB. (a little over half of mine had them) Launched Kung Fu Panda, and it worked flawlessly. Without ANY adjustments being made inside PCSX2. For the few PS2 games I have, if KFP works, they'll all work.

Try removing Complete all-together, then click the Games tab and see if any populate. It should populate. (If not, there's other issues) Now add Complete back in and set to Is Not Empty. Check the Games tab again. It should populate. Back to Auto-Populate, set Complete to False. Check the Games tab again. Does it populate? Weird, but this worked for me.

If you're just wanting to get a single game (pacman.zip) added, you could just click the plus sign (+) in the lower right corner of LaunchBox and add it manually. This seems to work exceptionally well. Especially since you know the name of the ROM file.

I think you mean to say "the current version of PCSX2, per-game config is built-in". To get it to launch correctly from LaunchBox, yes. As you've read in this thread, the old "--fullscreen" command-line parameter is now "-fullscreen" (single, not double dash). But you can get rid of that completely by checking 'start fullscreen' (or however it's written) in the PCSX2 GUI. Also, using the command "-batch" (without quotes) will alleviate the need for an exit script. Lastly, (and pretty important) if you have (had) any per-game custom command-line parameters to load specific configs, delete those. Are you having specific issues running PCSX2? Or just generally asking if you need to do things mentioned above?

LaunchBox does have something like you're asking for. At least for the popup windows/dialogs. I'm not sure if BigBox does.

I'm not really sure what you mean. I'm pretty sure all these do is, when you're in-game and press Tab to bring up the MAME Menu (at least in stand-alone MAME), then select inputs, instead of showing something like Player1 Button1 Player1 Button2 it'll show you (if available) what the action is Player1 Punch Player1 Jump Also in stand-alone MAME, when you open the emulator without a ROM, you can scroll sideways on the "Infos" tab to "Command" to see commands for a particular game. I've seen these buttons in color, but never figured out how to have them show that way in my MAME.

If you have ROM specific ini files that you created in your old MAME setup, they're most likely in something like "D:\Old_MAME_Setup\ini\" folder. Simply copy those ini files to your new MAME folder. Something like "D:\LaunchBox\Emulators\MAME 0.246\ini\" If by chance you're talking about ROM (game) specific settings you had in your old MAME such as keyboard/controller bindings, those are .cfg files. If you want to copy those over, do the same as above but change "ini" to "cfg" in the file paths.

Look at the LaunchBox debug Log file and see if it indicates any issues with it there. Also, you may want to make things "public".

No need to install AHK. You can use the AutoHotkey.exe located in ../LaunchBox/ThirdParty/AutoHotkey/AutoHotkey.exe and then the "full/path/name of your script.ahk" as the Command Line Parameter. "D:\LaunchBox\ThirdParty\AutoHotkey\AutoHotkey.exe" "D:\Utils\My Awesome Scripts\TheBestOneEver.ahk" Be sure to use quotes. Especially if your path has spaces in it.

Don't know about retroArch, but for stand-alone MAME, command.dat would go in the ../MAME/dat/ folder, and command.ini would go in either ../MAME/ini/ or ../MAME/ini/folders/ Depending how you have it setup.

To load DemulShooter with a game, you can add an Additional App to the game (edit the game in LaunchBox), and point directly to demulshooter.exe. Set it to run Before Main Application.

Just a guess for a potential solution, from your screenshot above, go to the Startup Screen section and turn off the startup screen. (Uncheck the box.)

I was just re-reading/remembering that, that is the way to go. @Denys06 You might want to read through this post. It's 6 pages and a couple years old, but holds a lot of good info about an emulator that itself hasn't been updated in a while.

Remove the ROM name from the Custom Command Line. LaunchBox puts that in for you.-run=gaelco -rom= -run=gaelco -rom= Also make sure your Emulator is setup correctly in LaunchBox. You'll want all 3 boxes checked.

I don't use the Demul emulator, but the 1st post says to "add it as an additional application that loads before or after your hikaru game and it will make it go fullscreen on load." So you may try it there instead of the Running Script section. But since all it's essentially doing is pressing Alt+Enter when the window is active, you could try a Running Script like: Loop { ifwinactive, ahk_exe demul.exe { send !{Enter} break } } ; This section closes Demul when pressing Escape $Esc:: { Send !{F4} } ...and not use the HikaruFullscreen.exe program at all. I'd be curious to if this works.

Based on you saying you want to replace them with your images ("my graphics"), you have the images you want to use. But you also said you're "hoping there was a local source", which can be read as you're looking for replacement images to use. I'm going to assume the prior (you have them). As Neil indicated, it is possible. Just remove the existing image and replace it with yours in the /LaunchBox/Images/Playlists/All Games/Clear Logo/ folder and in the /LaunchBox/Images/Playlists/Favorites/Clear Logo/ folder respectively. Option "B" (Do it from within LaunchBox itself) In LaunchBox, Right click on your "Favorites" playlist (on the lefthand side) and click Edit... Drag the image you want to use onto the Images section (right side of the Edit Playlist window). Click the image type and change it to Clear Logo. Click the 'left chevron' to navigate to the "default image", then click the "X" to delete it. (you'll now have 1/1 [one of one] images showing) Click OK to save and close. Do the same for the "All Games" playlist you created. (Not to be confused with the "ALL" playlist, which isn't really a playlist anyway. Besides, it can't be edited.)

There's a Pause Theme floating around that will display the Controls Information image. (Don't recall if it's generic controls, game specific, or both) Similar to CPWizard's MAME pause feature. But not as a 'menu item'. It simple shows the image in with the Theme. I've also seen a modified Startup Theme that does the same thing. I've seen an AutoHotkey script that's used in leu of MAME as the emulator that will show a full screen 'splash' of your game-specific Controls Information image, until you press a key. After the key press, MAME is started, loading your ROM as normal. This one takes a little bit of "creative licensing" to work. But viable none-the-less. Of course, all 3 of these require that you already have all the control images. How far are you willing to go? Well, 2 years, I guess. lol I know one (or several) users have created Console (vs Arcade) specific controller images to go with the Pause Theme above. Are you wanting to create something that will auto generate on-the-fly, images? I think CPW may have done that [for Arcade]. Hmm... maybe not on-the-fly. But the auto generate is (was) cool! I'm intrigued to see where your idea takes you.

It's not so much because your unfamiliar with AutoHotkey, it's because that's as much as you're going to able to do. "close". When an emulator has a built-in Reset feature, the emulator stays active while resetting. As in, it doesn't completely exit then restart. If you were to add AHK code to the Reset Game Script section of your CEMU emulator (or any emulator for that matter) that closes, then restarts then emulator, you'll have a couple issues. When your script goes to restart the emulator, there is no viable way to tell it to restart using the same ROM you originally launched with. This is the big one... When LB/BB sees the emulator close, ALL scripts are abandoned. So even though your script might 'say' WinClose CEMU... Run CEMU..., when executed through LB/BB, it will never see the latter half. And even if those weren't issues, it's probably just as easy to exit and then restart the game, normally.

We're all special in our own way. lol Tested again (a couple times) and my Close Active Window button-combo does indeed close BigBox.

In my 1 quick test this morning, it did close BB for me. But I hadn't finished my 1st cup of coffee yet when I tested. I've been wrong before. and as life has shown, I'll be wrong again. And I will be the 1st to admit it. I'll check again in a bit. If what you're saying is true, then NikoDirkFan shouldn't having an issue unless "Exit" was also bound to the Guide Button.