dragon57

The Bezel Project app from the Github site does not interact with the Launchbox ability to install the same bezels. They are two ways of accomplishing the same thing. If you are a user of Launchbox, it is best to use its built-in logic to install the bezels. The separate app was written first and is intended to help others who use different front-ends to install the bezel packs into their installation of Retroarch. Since you never really answered my questions, I can't help much beyond this point. The overall sequence of using the app is to install it, configure the paths and preferences, select option 1, select which installation method to use, ie, native MAME, Retroarch, Rocketlauncher, then select which bezel packs to install on the subsequent screen by clicking on the system names presented in the combo box list. Option 2 and 3 are for advanced users and normally aren't used in normal operation, but are provided as an assist if you want to disable, then enable a bezel pack later, for whatever reason. I hope the video you found has helped you out. If you have any further questions, please be specific in your questions providing what you want to do and for what system.

You seem to be missing a screenshot that would be displayed after selecting the OK button on the first screen. I am also assuming you have already installed a bezel pack? If so, you don't need to enable it as that is done automatically during the initial install. If you have installed a bezel pack, then later disabled it using option 3, then the missing screen shot should have shown all the installed bezel packs and their current status. If you don't select which bezel pack to enable, then you will get the popup shown in the popup with the red X on it. Can you show the missing screen so I can further diagnose the status of your bezel installations?

Could you please post a pic showing this text string and explain what you are attempting to do?

All, a themed bezel pack for the Atari ST has just been released. Also, the issue where the Bezel Project app for Windows disables the overlays setting in Retroarch has finally been identified. A new build of the app is forthcoming, but no date can be given at this time. 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

Thanks for posting this solution so others can benefit. I only recently started receiving comments the Bezel Project App was turning off overlays. I knew it didn't originally do this, so I was baffled what could be doing this. It took a deep dive through my source history and versions of Retroarch to figure it out. Initially, I had to make several assumptions about Retroarch and its configuration parameters. Everything was fine until relatively recently. As the Retroarch devs are wont to do, they changed and added many overlay-related settings. The fix is simple, but I'm in the middle of refactoring all my code, so not sure when a new version of the Bezel Project app can be posted, but I'm aware now, and a fix it in the pipe, so to speak. Thanks again.

Using MAME ini files named for the software list systems is the way to go, IMO. Been doing it that way for years. Seems to be more frontend agnostic that way too.

As with the original post, more info/pics are needed so your question can be answered. Is this in LaunchBox, BigBox? Are you using the default theme(s)?

Not sure how this will help, and assuming you don't want to get down into weeds of the actual compression algorithm used to create the chd file (hint: there are different versions supported by chdman, the MAME utility originally used, mostly likely, to create the chd files). Think of chd as another type of compression format like zip, 7z, rar, etc. A utility like chdman is used to create the file, then the end user program like MAME, and the other emulators that now support CHD, decompress the CHD file 'on the fly' directly into memory so the emulator can use it. Does any of this help?

The Bezel Project files are not compatible with vertical monitors, sorry.

If you are willing to use something outside of LaunchBox, you can use something like Notepad++ under the "Find in files" tab to mass edit by replacing all the directory references in the XML files. Make sure LaunchBox is not running if you do this.

Do your rom names exactly match the names of the overlays/bezel files?

You could always use a symbolic link/junction for this. Use the HardLinkShellExt utility.

The app isn't supposed to do that. I will have to do some testing here to see what is going on. The app hasn't changed in a very long time. No one else has mentioned the symptoms, but doesn't mean much in the real world. Thanks for bringing this to my attention. I will report back.

The app does not turn that option off, per sec, but it does copy the default retroarch.cfg file, so if you haven't turned that option on and saved that in your default settings, you will see that behavior.

Are you talking about installing Bezels with the Bezel Project Windows App, or via LaunchBox?

MAME's bezels should be located in the 'artwork' directory directly underneath the main MAME directory.

All, a themed bezel pack for Atari 800 has just been released.

Not sure why the zip option isn't working for you. Works fine here. I just tested with random repositories.

This site has a few: https://www.verticalarcade.com/overlays/all-overlays

EmuMovies has some 16:9 platform videos on their ftp site under /Official/Platform Videos.

Really not sure then. I switched cores to Gearcoleco and renamed the bios rom file and Retroarch runs all my Coleco games with no issue. Just for info, I'm running Retroarch 1.16 and Gearcoleco 1.0.1.

What name is your bios rom file? Gearcoleco requires colecovision.rom.