dragon57

While the Launchbox database isn't tied, per se, to the No-Intro naming scheme, I have found if you start with a set of games that are already named per the No-Intro database, you will have much better coverage when Launchbox tries to download media. I just created a new DS platform and told Launchbox to download box - 3d, box - front, cart - front images, screenshot - game title and clear logos. This started from a No-Intro DS set consisting of 1563 titles. This was only from the Launchbox database and didn't include anything from EmuMovies. Edit: I added EmuMovies and those totals are in parentheses. Here is a count of the number and type of files downloaded. Box - 3D: 1545 (w/EmuMovies, 1554) Box - Front: 1546 (w/EmuMovies, 1554) Cart - Front: 1421 (w/EmuMovies, 1439) Screenshot - Game Title: 1326 Clear Logo: 1526 (w/EmuMovies, 1553) As you can see, I got nearly full coverage. The only ones with missing media were the multi-game carts and a few homebrew that aren't official anyway, although there were a couple I had to manually tweak in the Edit Game panel to force a match. If you want to see what is contained in the LaunchBox database for a particular platform, the easiest way is to make sure LaunchBox and/or BigBox are not running, then use a SQLite editor to open the LaunchBox.Metadata.db file found in the Metadata folder. You can perform a select statement for the platform in question for any or all the fields in the database. Make sure you only perform a read-only query and don't change anything while accessing that file.

I suspect the issue is your naming of the zip files. Normally the name will be the same as the file being compressed and not with the .nds appended to the overall name. Example: LEGO Batman 2 - DC Super Heroes (E).zip and not LEGO Batman 2 - DC Super Heroes (E).nds.zip Have you tried the naming I gave in the example?

You can find an XBox bezel in this directory, plus a ton of other systems. https://github.com/libretro/overlay-borders/tree/master/16x9 Collections/NyNy77 1080 Bezel

I could have used something like this years ago. I work in the different platforms virtually every day. I finally resorted to just searching the database using the platform: option, but an alpha option would be huge.

I don't see any issues downloading from Github specifically. I'm a member of the Bezel Project and all the bezel tests work fine and fast. It could be related to your ISP, or a million other things, but I agree, you shouldn't be seeing such a big delay. The only option I can think of is to cancel the LaunchBox downloads and try using the Windows app we provide on the Github page and see if you still see a delay. You can try the app from this link: https://github.com/thebezelproject/BezelProject-Windows

I run Atari ST under Retroarch quite often using the Hatari core. Never had an issue, but a tos image as you say is key. Below is the section from the hatari info file with some info. # Firmware / BIOS firmware_count = 1 firmware0_desc = "tos.img (TOS 1.02 US aka Mega TOS)" firmware0_path = "tos.img" firmware0_opt = "false" notes = "(!) tos.img (md5): c1c57ce48e8ee4135885cee9e63a68a2"

Zom, IRL issues always should trump other things. My contributions here as far as uploading various art related archives have basically stopped because of my own RL issues. I still try to weigh in on Bezel related questions because I still am a member of The Bezel Project team, but that too has slowed down. Try not to let users get you down. Thanks for all you do and have done in the past. We are all the better for those things.

As was said upper in this thread, ES-DE is probably the best choice, with Attract Mode being 2nd. Both work very well under Linux. ES-DE can be found here: https://es-de.org Attract Mode can be found on its homepage and the latest fork, the Plus version is here: https://github.com/oomek/attractplus

It has previously been reported the lay files for vertical games in MAME are bugged. You will either have to manually edit them until the LaunchBox team corrects this, or use the Bezel Project Windows app to install the MAME bezels, which should be correct. I have attached a lay file for vertical MAME games you can use for reference to your lay files. Default.lay

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.