dragon57

Not at the source. The Bezel Project doesn't pull lay files for MAME roms itself, but calculates those on the fly as native MAME bezels are installed. There must be a glitch in LB somewhere.

If I'm not mistaken, RocketLauncher has an Attract Mode plugin, right? So you have a great solution there, as you have already intimated.

An updated themed and system art bezel pack for the Commodore Amiga CD32 has been released, and the game list for Launchbox has been updated.

An updated themed and system art bezel pack for the Commodore Amiga and the Panasonic 3DO has been released, and the game list for Launchbox has been updated.

Some of your items are addressed in this thread: As to your 'to zip' or 'not to zip' is user preference, but you have to realize how some things will be affected by either choice. I personally 7-zip all my console roms, but many find it easier to just have no of the small console roms compressed as large disk drives are pretty cheap these days. There is no right or wrong here.

While the TV surround can cause a very slight clipping if you don't use a shader to match the round corners like CRT-GEOM (the intent of that TV surround), what you are seeing is way more than you should have. What does your lay file look like for this game? Here is mine. <!-- bezel.lay --> <mamelayout version="2"> <element name="bezel"> <image file="bezel.png" /> </element> <view name="Bezel Artwork"> <element ref="bezel"> <bounds left="0" top="0" right="16" bottom="9" /> </element> <screen index="0"> <bounds left="4.625" top="0" right="11.375" bottom="9" /> </screen> </view> </mamelayout>

LaunchBox pulls from the same Github, so updating with LB should be fine.

Have you updated your bezels for MAME very recently? The new ones we just pushed to Github should have correct lay files for all the vertical games.

Note: the MAME bezels were just updated a couple of weeks ago. Depending on the age of your files, you may want to reinstall them. Here is my lay file: <!-- bezel.lay --> <mamelayout version="2"> <element name="bezel"> <image file="bezel.png" /> </element> <view name="Bezel Artwork"> <element ref="bezel"> <bounds left="0" top="0" right="16" bottom="9" /> </element> <screen index="0"> <bounds left="4.625" top="0" right="11.375" bottom="9" /> </screen> </view> </mamelayout>

Yes, should not be a problem. Did you download just png files, or a matching set of cfg and png files for each system? Show us a pic of what you downloaded and where you put them.

Here is how mine is setup.

Totally agree. Retroarch has a ton of tweaks you can do, but unless you have lived and breathed Retroarch/Libretro over time and understood those tweaks as they evolve, it can be difficult for users to figure things out in a simple way. Keep giving us data and info and I am sure this can be figured out.

I have seen a number of people who say behavior seems to change when launching Retroarch from LaunchBox versus launching from Windows. Not always, but usually it is related to what is defined in the command line arguments for the Retroarch Emulator section. Have you checked to see how LaunchBox is launching Retroarch? I doubt that command line is basically blank.

This has been a bane to all users of Windows Retroarch and the cores that support more than one system. I work on the Bezel Project team and am well aware of this issue and I am currently working on a solution to this. My testers have told me my latest method works well for them and I hope to roll this out in my Bezel Project Windows app very soon. While my efforts address the issue you bring up more widely than just for bezels, my bezel solution should address what you are stating. I have reached out to the LaunchBox team about integrating my new method, but I can't say more than that at the moment. I have no timeline yet for broad release. Just know a potential solution is forthcoming.

My Bezel Project for Windows app supports writing out the config and overlays directories along with a readme file that SHOULD work on your android device (at least I have no reports recently that it no longer works). You can download the app from here: https://github.com/thebezelproject/BezelProject-Windows As far as I know, LaunchBox does not as of now support Bezels on Android.

All, an updated themed and system art bezel pack for MAME has just been released. This builds on the original MAME sets that were targeting an older Retropi build. These updates attempt to provide a bezel for every 'working' game MAME supports as of the 0.270 release. If you happen upon a game that is missing a bezel, please go to Github for the particular repo in question and open an 'issue' ticket with what is being requested. Also, the issue where the Bezel Project app for Windows disables the overlays setting in Retroarch has finally been identified and should be fixed. A new build of the app (V1.1.13) has been uploaded. Existing installations of the app should reinstall this new release as it contains a new file required for MAME. The app has better support for native MAME installations for games that use more than one monitor for its display. If you want to know when a new version of the app is released, follow this post as I will be announcing it here. You can also watch the repository on Github: https://github.com/thebezelproject/BezelProject-Windows Finally, the game list required for LaunchBox has also been updated.

You have two options in my mind. 1. Do some manual pixel offset measuring in a graphics program using those bezels in question, then edit the MAME lay file for the same bezels, then you should be good. 2. Go into the MAME Tab section with the bezel showing and modify the video graphics settings to get the MAME viewport to fit the bezel transparent display port section.

That indeed is the correct flow. #3 is a big pain point for our Bezel Project. I plan to see what I can do about that sometime coming up. All the old requested bezel repos for consoles/system will be done very, very soon (probably a week). Then the plan is to hit every repo for outstanding issues and see if a bullet point structure will alleviate the problem of using a core for multiple systems.

It sounds like you have a core cfg file saved with menu_show_overlays set to false. You will have to force save an updated core cfg file inside of Retroarch after changing this to true, or manually change the value inside the questioned cfg files (make sure Retroarch isn't running if you manually edit anything).

There are already quite a few Sord M5 silver rings already made and submitted. They are in the thread and in my Silver Ring additions pack in the download section.

Here is the current structure of the SQLite dB, if it helps.

I assume if you want to look at the insides, you just use one of the SQLite tools to lookup and edit the tables. I am sure this is not supported, but I have played around inside of the LaunchBox.Metadata.dB file (never do this with LB or BB running and make a backup first) and had success editing areas/data myself. This is the one I use:

Here is one I created years ago. Take your pick. Res is 2424x455

This set in the Downloads/Platforms section has one for Super Famicom.

EmuMovies has pretty good coverage for the older cartridge-based systems, but you will find some holes here and there. As I've seen with most sites with manuals, the coverage tends to go down as you approach newer system files. I just re-checked for the Atari cartridge systems and most are available on EM. Commodore 64 shows 973 manuals. Your mileage may vary depending on what games you have in your collection.