dragon57

While I know my following comment is not helpful, I will take your request and put it on my to-do list. Since 21:9 monitors still account for a very small percentage of overall monitor sizes in current Steam statistics, I believe having at least a generic MAME bezel for horizontal and vertical games would be better than nothing. Please don't take my comment as an official direction by The Bezel Project. It is not. I will see what I can do about generating a default MAME horiz/vert 21:9 bezel and posting here, hopefully before the end of the year. No promises, however, as this is a busy time.

Correct. The latest Bezel Project Windows app creates MAME lay files according to the correct instructions mentioned above. While LaunchBox uses and installs files from the Github repositories as the BP app, lay files are created by Launchbox itself via the devs here and I have no idea if their lay file logic was changed. You could always use the Report a Bug feature of the forums, which is under the Help & Support header if you find Launchbox's latest beta writes out lay files incorrectly.

As long as the symlink is correct and still accessible to the OS and apps, you should have no problem. That is the purpose of symlinks, to do what you are needing to do.

Another 100% in agreement. Hands off everything gaming related unless the user turns on an option. I can't tell you how many friends have enough trouble keeping retroarch running without another app coming along and shooting both feet and kneecaps off.

A new Windows installer, V1.1.15, has been pushed to Github which should write out MAME lay files in the modified format.

Many thanks for pointing this out. I will create an item in the project to address the lay file format as you stated.

So you are saying you must type a name in that field before selecting Browse? If so, indicating that would be super helpful. Also, if the name is required first, could the browse button be inactive until the field is satisfied?

I also come from an IT related team with a QA background. I made a personal decision to stay with an old build because recent updated releases of Launchbox had a number of issues with my installations. I have been too busy to provide feedback, but after searching the beta threads, the issues I saw were already reported. Your points are quite valid. I hope someone from the core team responds.

Down again. Whoever is responsible for the server might want to check for a root cause, assuming no server admin tasks are going on to cause this.

Seems to be fine now. Thanks for the follow-up.

The DB seems to be down again. This is what I get when I search: An unexpected error occurred while processing your request. I've been trying for nearly an hour. Thanks!

I highly recommend this utility: https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html I have used it for a number of years. While you can create everything manually in Windows, this util makes things easy.

Would you be adverse to just creating something like a hard link or junction back to the default location? I mess around with retroarch defaults all the time and have tried this successfully.

Perhaps a strange choice, but I would pick Arkanoid or DX-Ball for the PC. I played the heck out of those and every time I happen on another variant I will play it without fail. Something about that play mechanic fits my mental grooves.

The example given does require a bit of retroarch knowledge. I didn't make it more specific because the Bezel app is used for more than just LaunchBox. As far as LaunchBox configuration using the latest Bezel app referred to in your post, you would use Tools/Manage Emulators, then select Retroarch and click on the Edit button. Find the Associated Platforms section, then the list of cores and "Extra command-line parameters. In that parameters section, use the -c option and the name of the cfg file created when the app installed the selected bezels. Look in the root Retroarch directory for a list of the cfg files available. Hope this helps. If not, give us a list of the cfg files available and a pic of the Associated Platforms panel.

Change Show inputs on Overlay to Off, then save a new config. Don't forget to overwrite the old cfg with the new one after you exit Retroarch.

You need to tell retroarch to load your config file for that core. Click on Associated Platforms and add something like this to the Extra command-line parameters: -c "config\melondsds_libretro.cfg" If your cfg file is in a different location, edit that example to match yours.

GearColeco only supports col, cv, bin, and rom extensions. Probably need to find different versions of those roms.

What does your retroarch command line look like?

Look for melonds_libretro.cfg in config and copy that to melondsds_libretro.cfg.

That is why no bezels are showing. Copy the cfg files from melonDS to your melonDS DS folder.

Works perfectly here using that core. Works fine using my normal core, desmume too. What is the directory named under config for your medondsds core cfg files? It should be "melonDS DS".

So, he has bezels showing for other platforms? If so, all I can recommend is that he compare his RetroArch installation with yours, since you are sharing files. Verify structures under config and overlays\GameBezels.