dragon57

OK, the overlay definition in MAME for Star Castle without any 3rd party bezels installed, like from our project, are in its defined logic for the game itself. The lay language allows defining rectangular and circular objects in the later versions of MAME (originally MAME used .art files for many overlays) without needing external graphic files. The only way to use Bezel Project files AND original overlay definitions is to combine the lay file contents in a way that combines all the definitions. I have all this info, but haven't ever performed the conversion required. I will work on your requirement and get back here with an attachment and explantion of how to use the attachment contents.

Not sure if this is close to what you are looking for, but I just whipped this up using the period default for the Konami logo and font.

It sounds like the only way to get your intended result is to combine the lay files and resulting graphic assets. If you don't have the MAME knowledge to do that, there are many here who could probably help out. Just reply and attach the assets you are using for both the overlay and bezel.

From my investigations of the past, there was never an official, or even an unofficial Konami Python logo. The Konami Python system was based on the Playstation 2 and was only a hardware designation. I suppose someone could just make one up, but we would need some kind of guidance as to what you were looking for.

As far as I know, Launchbox can't handle the WBFS naming convention. I can tell you what I did ages ago and it worked for me. I had a full file listing of all the known Wii WBFS file names and the associated 'real' file name, example: R5PE69 = Harry Potter and the Order of the Phoenix I wrote a script to create shortcuts that used the long file names in the shortcut naming and the shortcut pointed to the WBFS files. I imported the shortcuts in Launchbox which allowed scraping using the long name, but ran the actual WBFS file. Hope this all makes sense.

On my Pixel 8 Pro, I have Launchbox installed at /storage/emulated/0/Launchbox I don't recall changing any settings to install it. Everything has always just worked.

Have you checked out his web site: https://www.verticalarcade.com/overlays/all-overlays

Good advice!

Just as a diagnostic step, have you tried installing on your C drive just to test if the same behavior follows drive/filesystems?

I just started using Ares and find using --no-file-prompt on the command line keeps that extra window from popping up, at least here it does.

You will have to manually turn on the option I mentioned, then save a core override file, but png and cfg files for Retroarch are not the same as for Duckstation. Duckstation uses png and yml files.

Very sorry, I misread and thought you were using Retroarch.

Is this with the latest beta version?

Do any bezels display when using that core? Have you verified the option to 'Display Overlay' is On under the On-screen Display section?

I recall that one, but no mention of a zip file error like this one.

It could be a bug, but strange that more users haven't mentioned it, but anything is possible. I also haven't received any DM's about LB bezel issues like I normally do. No mention in our Facebook group either. I look forward to finding out what is up.

That works as well as long as you never change your rom set out, but in the end, whatever works best for you. Just for your information, we use the No-Intro naming standard for cartridge based systems, the Redump naming for systems with optical media, then we fall back to TOSEC naming for computers.

I did forget to mention one thing. V1.1.13 of the Windows app uses the same configuration logic as LaunchBox, so that version should be used unless you specifically want the new install logic that mimics the configuration used on the Linux platform that avoids naming conflicts that can arise if you use Retroarch cores that support more than one system, V1.1.14. Finally, the latest version, 1.1.15 addresses and uses the correct MAME lay file logic.

Using the Bezel Project Windows app should not matter to LB once the files are installed. They go to the same location. The only thing you might have to do is rename your roms to match the bezel names, but if you are using standard rom packs, that shouldn't be necessary either.

Very strange. I know the LB release one version back had issues with bezels, but the older ones were reported to work. If I come up with anything else I'll post here.

That is correct. That app is an all or nothing approach. For what it is worth, we polled our user base at the time and most downloaded full No-Intro sets, so we packaged both the Linux and Windows apps to provide that.

I forgot to ask and I assume you have tried different builds of LB as the different versions came out? How far back have you tried?

You should never have to run LB and/or BB as admin, but at least that is a good data point to have. The only thing I can think of as a way of diagnosing all possibilities is to try using the Bezel Project Windows app and try installing bezels for a platform that you already know causes you problems using LB. That will verify your ISP isn't causing download issues from Github, which is where the files originate from.

The Naomi logo requested already exists here in the thread and the Additions archive available for download. Below are the others requested.

Here is one using the latest branding logo.