JoeViking245

Um... that looks kind of like a RetroArch config file. Not [stand-alone] MAME. Where exactly did you find it?

The 'good' screenshot you show is text vs images (Clear Logos). So if it was bad, then there'd really be issues. You illuded towards that you tried the Default theme. That was going to be my next suggestion (and the one recommended to do this type of debugging with). If your Display settings are set to 100% and the 'Recommended' resolution, I'm inclined to lean towards it being a video-card-type issue. RE: the recommended resolution thing, I recall on my new LG tv that when I first hooked my cab up to it, the recommended setting was something other than 1920x1080. Without paying attention to what it was that 'it suggested', I switched it to 1920x1080. Might be something else to look at. What are your computer specs (including video card) that you have hooked to the TV? I presume you're connecting via HDMI.?. Does the PC you're using have its own monitor you can test on? Does it show the same results?

With your non-merged set, you have all the ROM files in one folder. Don't you? They should be. And if obtained from a 'reputable' source, file names should be good. Galaga (parent ROM 'galaga.zip' [Namco Rev. B]) does also require 2 device files 'namco51.zip' and 'namco54.zip'. But even the clones (right-click, play version...) require at least namco51. Most clones require both. Those 2 device files should [already] be in the same folder with all the MAME ROMs. In one folder. If you switch to a merged set, the device files [the files within namco51.zip and namco54.zip] will be inside galaga.zip. As well as files for the 6 clones.

Also, for your Default Command-line Parameters, try adding -rompath %romlocation% after -keyboardprovider dinput and see if that helps. -keyboardprovider dinput -rompath %romlocation%

Thanks! That works. Well, if you do a little backtracking. Using MAME revision 0.226 mame64 m5 -ram 36k drops

Saw an example on their GitHub site showing to use -e Then point to the eboot.bin file. fpPS4.exe -e "D:\LaunchBox\Games\PS4\undertaleextract\Pvini-CUSA09415-Undertale\CUSA09415\eboot.bin" Other parameters found:

Nah, it's still there. Un-check the box. Or set everything (or just some) to None.

What do you have your display scaling set to (Windows Display Settings)? If you set it 100%, does it still show the clear logos partially blacked (blocked) out? Is the display resolution set to [whatever's] recommended? (working on process of elimination)

Glad you got it to work! At least with one controller. I only have an original 360 controller (wireless), so can't attest to the other. It looks like the Power A is a corded controller. So it may be related to what @skizzosjt was mentioning regarding the joy number (not to be confused with the Button #). That is, it might be being seen as Joy controller #2, or #4 or something other than 1Joy. So "1Joy6" may need to be "2Joy6" or "4Joy6".

MAME ROMs don't have any required associated mp4 files with them. If your ROMs folder for MAME contains .mp4 files, I might question your ROMs source. And yes, you can remove .mp4 files located in with your MAME ROMs without affecting the games. That said, videos that you're seeing in LaunchBox would (should) be located in your ..\LaunchBox\Videos\[name of platform]\ folder.

Well, looking at this last post, I might suggest keeping the cat from walking on the keyboard. Missing the screenshot of the Details section. Though not sure It's going to help much. The screen that's popping up is triggered (by default) by pressing Shift+F7. Not sure if it can be triggered by turning on AutoSave, especially when loading a game (vs exiting). My next thought was maybe you have a key stuck on the keyboard. But you'd have to have 2 stuck unless you remapped the default key press(es). Also, it'd trigger when loading from MAME itself. If that doesn't lead you to any thoughts of possibly something you changed or may have done, you could ty doing a fresh install of MAME. Beyond that, I'm out of ideas.

(Should be able to take a screenshot of the message by pressing "Print Screen", then [here] when typing your message, press Ctrl+V to paste the image) I'm still not sure what the 'box with save state' is that's opening when you launch a game. Does it say anything other than 'save state'? Does it give you options to select a save state to load? Or is it something you just have to click to close? Or does it automatically close on its own? Sorry. Again, I've just never seen anything related to 'save state' open when launching a game. My next question was going to be if you could edit your MAME emulator (in LaunchBox) and share a screenshot of the Details section and one of the Running Script section. If you have the Edit Emulator window open, you can take a screenshot of just that window by pressing Alt+PrintScreen. And then press Ctrl+V in your message reply. You know, they say a picture's worth a thousand words.

Be sure you're pressing (and hold) the Left-Button (Joy5) BEFORE pressing the Right-Button (Joy6).

The 'formula' for the answer to your question is quite literally right above your post. Here, you'll need to press (and hold) Button 7 before pressing Button 8. 1Joy8:: If GetKeyState("Joy7") { Send, !{F4} } You can replace the 3rd line with WinClose, ahk_exe rpcs3.exe, as necessary. To make it "just for rpcs3", place it in the Running Script section (as you had previously done). You can add it below (or above. doesn't matter) your existing Escape sequence to give you 'options'. i.e. Use the keyboard OR the controller.

If you have the -rompath command-line parameter in your MAME's Default Commandline Parameters (LaunchBox, Tools, Manage, Emulators, MAME), it will override mame.ini's rompath. Remove that parameter and its' variable and MAME will use the rompath, as listed in mame.ini.

The %romlocation% variable was added to (built-in to) LaunchBox sometime early 2022. Its resulting value is "C:\Path\To\Rom\" (with quotes), based on the games path. Other command-line variables LaunchBox makes available are: %romfile% %platform% %launchboxorbigboxexepath% %gameid%

Can you share a screenshot of the 'Save State box'? Can't I have ever seen that when launching a game. Does it appear with any of the arcade games you launch? If you run MAME by itself then start a game from it, does the box still appear? When you installed MAME, did you have LaunchBox install it? Or install it yourself from the file from MAMEDev?

Apologies. Didn't notice the folder you were in at the top of your 1st image.

Responded in your other post.

Under \LaunchBox\Images\Platform Icons\, try putting them inside their respective subfolder(s). Might be able to select the platform then press F5 to refresh those images. If not, restart LaunchBox.

Don't know about Categories. Never tried. Pretty sure it'll only work on Platforms. I don't mess with hierarchies at all, but if you can have a 'Ports' Platform under your Windows Platform, it might just work. But if you put this into the Windows Platform, couldn't you just have it be a 'game' in Windows instead?

Just tested with [a copy of] the Default Theme and also with Hypermax Refried on LB/BB v13.10 and everything worked as expected. If you go to \LaunchBox\Plugins\LaunchPlatform\, is there a text file in there named after the Platform that has only the one 'game' in it? aka, the platform that you added on Step #2 in Launch Platform Setup.

Were the other Themes that were tested and worked, tested on the cab? (vs. a different PC) Did you, could you test others on the cab? (more process of elimination)

Did you add the line at the bottom also? (have to ask) Also, just curious, did the Setup add those 2 lines for you (and create the backup files 1st)? I didn't study the Theme's xml file. Hopefully it isn't trying to use the backuped files. I doubt the Theme author would be able to help (because of my plugin changes). But would be cool if they had the answer. Are you using a view that uses the [new] PlatformWheelxxx? Maybe try a different View (for process of elimination).