JoeViking245

Thanks! 😊 That's what we like to hear. You're welcome. Always glad to help and glad to hear it's all working. Now go play some games!

Here's some more reading for you. Media Packs - LaunchBox Here's an option: ..\LaunchBox\Images\Media Packs\Overrides\Platform Clear Logos\Platform Categories\ ..\LaunchBox\Images\Media Packs\Overrides\Platform Clear Logos\Platforms\

Simplicity is good.

Those 2 images are "Banner" and "Clear Logo". For these, it'd be a lot easier to edit the category and add those images there. Click the yellow +, select the image then set the type. LaunchBox will do the rest of the work, saving them in the correct location.

Looks like for everybody and anybody.

Yeah, all I can say is it's still being looked into. I may end up doing something cheesy like keep track of playtime myself, then on game exit, tack it onto the game's playtime. But I ain't willing to resort to something like that just yet. Thanks for testing.

I don't know "the" answer. But might try checking/un-checking these 3 options and see if any combination there-of fixes it. Myself, I'd stick with DuckStation. But that's a personal opinion.

I thought you were using the same "_Emulators\MAME 0.289\mame.exe" for both instances in LB which would have read the same mame.ini file. Which in turn directs MAME to where [all] the ROMs are located. My guess is in the Details section, the Default Command-lime Parameters contain -rompath %romlocation%. That said, you could un-edit the mame.ini and then add this to the aes parameters and it will work. e.g. -rompath %romlocation% aes %romfile% -bios usa This [added] parameter is telling MAME that the ROM files (-rompath) for the game being launched are in the same location as the ROM (%romlocation%). Regardless, it's working now. It doesn't say anything about "missing files". It mentioned "incorrect" files. Semantics matter when trying to troubleshoot. It might be with your -bios usa parameter. I've only ever seen it be -bios and then a number. e.g. -bios 16 I'm not saying "usa" is invalid. I just don't know if it is valid. In the spirit of troubleshooting: Try removing that part and see if that message still appears. If not, then try my example. If that doesn't resolve it (the message still appears), this usually means that you have a mismatched set. Like maybe mame.exe is version 0.289 and your ROMs are version 0.288.

I don't have any magazines in my collection, but this should help some: https://unbrokensoftware.github.io/launchbox-reader-releases/getting-started.html

Your rompath in mame.ini points to this folder (/roms/). It also points to where all your ROMs are located (/MAME ROMs (merged)/). Copying the 2 ROM files here, MAME can see them, but it can also see them in the 'other' folder. Making this an unnecessary duplicative effort. I think you're saying you added a 'new' emulator in LaunchBox ("MAME 0.289 Neo Geo AES") and it points to the same exe file as your 'original' MAME emulator you have setup in LB. So, 2 separate emulators in LaunchBox, both using the same MAME exe, mame.ini, folders etc.. If that's the case, this is where (if you're so inclined), you could use just the 'original' emulator. Since these [AES] games are in their own platform, in the 'original' emulators Associated Platforms section, you can add that 'new' platform, the parameters for it and check the Default box. This way, only games that are in this 'new' platform (shown "Neo Geo AES") will use the "aes..." parameters. Any game that's in the Arcade platform (or in a playlist where that game comes from the Arcade platform) will use whatever parameters are shown in the Details section. Eliminating the need for the 'new' emulator (aka essentially duplicative emulators). The fact that both Platforms use the same ROMs is insignificant. To clarify, once you've pressed the "any key", do the games run (are they playable)?

Since you're trying to revive a 'corrupted' setup, resetting your LB/BB settings shouldn't be "painful". Close LB. Make sure it's completely not running (e.g. Task Manager - Details) Delete: \LaunchBox\Data\Settings.xml \LaunchBox\Data\BigBoxSettings.xml Start LaunchBox.

One way, though may not "look" easy (but really, it is) is to: Select your SNK NEO GEO MVS playlist Select all games in that playlist (click one, then press Ctrl+A) Tools < File Management < Export/Copy ROM Files from Selected Games to New Folder... Copy them to a new (temp) location Import those ROMs into a new Platform "SNK NEO GEO AES" Once done, Select the new platform Select all games Tools < File Management < Change ROMs Folder Path for Selected Games... Select the original ROMs folder You can now delete the temp folder/files you created Now edit your MAME emulator (in LaunchBox) and under Associated Platforms, add the new platform and put in the Default Command line Parameters to start those games as AES (which off hand, I don't know what they are. But should give you a good start towards your endeavors).

I didn't notice anything in the Latest Changes for it (but that doesn't mean I didn't miss it). It was but a few hours before 14.0 was released I apprised the developers.

Parameters can be found here: Command Line Reference | LaunchBox Reader Make sure you have the spaces in between them and they're spelled correctly. These ones worked for me. -theme sepia -fixed-margin none -fit width -layout spread -fullscreen

One means of doing this is to (as you thought) add the reader as an emulator.

There's also \Media Packs\Platform Icons\Nostalgic Platform Icons\Platforms\my platform name.png \Media Packs\Platform Icons\Nostalgic Platform Icons\Playlists\my playlist name.png

There was a change in accessing what the latest version available for RPCS3 is. The developers are aware.

You still can't nest a platform under another platform though. The fix for having nice icons: If you have a premium account, you can add your own custom category icons. ..\LaunchBox\Images\Media Packs\Platform Icons\Nostalgic Platform Icons\Platform Categories\my category name.png

Copy one of your bezel.ini files and one of you bezel.png files and place them directly inside your /Bezels/Nintendo 64/ folder. Rename the files to "Nintendo 64" (with their appropriate file extension). Then when you run setup, the file names and a preview image will appear [for that platform].

From The LaunchBox Strategy Guide under LaunchBox for Windows, give this a read. It should get you in the right direction. Additional Apps - LaunchBox

You and me both. There is also a Show LaunchBox in Controller Mappings. Though should be {None} by default, worth checking. (maybe something happened when "reconfiguring button controls in [...] Bigbox"?) Is your encoder set to Keyboard mode or Xinput mode? This is the 1st time I've heard of this happening in my 8 years here. So it's an odd one to say the least. Other than something triggering Show LaunchBox, the only thing I can think of would be, however you're starting Big Box, it's like the key (or whatever) is stuck. Say, you select the icon on your desktop and press Enter, the Enter key is being "held" down causing repeated "presses". Not saying you're doing that. It's just the effect that seems to be occurring.

I spent some time trying to be thorough with the instructions on the download description. Please read through it all. It also looks like you may not have a "Nintendo 64" bezel folder (maybe you do) and you don't have a "Nintendo 64.png" bezel file.

In the interim, if you already have your own bezel files, there is a plugin available to add bezels to emulators that don't natively support them. And proudly made without the use of ChatGPT or Gemini.

It may be sending them consecutively too fast. Try adding a delay between the 2 key presses. Sleep, 3000 SetKeyDelay, -1, 110 Send {F11} Sleep, 1000 Send {F1} Return