BezelProject bezels don't display after installation
-
I installed bezels for nes, snes and mame using the installer. The images are there and I confirmed the images are in the correct directory but they don't show up in any of the cores.
Pi Model or other hardware:3B+
Power Supply used: Canakit 5v 2.5a
RetroPie Version Used: v4.8.9 on Buster and Retroarch 1.19.1
Built From: RetroPie website
USB Devices connected: Ultimarc mini
Controller used: Ultimarc mini - 8 game buttons, spinner, trackball, joystick, 4 admin buttons with ipac hot key (select, start, pause, enter, exit)
Error messages received: na
Verbose log (if relevant): na
Guide used: na
File: na
Emulator: lr-fceumm, lr-snes9x2010, lr-mame2010
Attachment of config files: https://pastebin.com/b6aLqhu4I don't know anything about pastebin. I assume this is what you need to view the file.
Why BezelProject loads over 3000 lines to a cfg file is beyond me.
Here is the mame cfg.Settings made here will only override settings in the global retroarch.cfg if placed above the #include line
input_overlay = "/opt/retropie/configs/all/retroarch/overlay/MAME-Horizontal.cfg"
input_overlay_opacity = "1.000000"input_remapping_directory = "/opt/retropie/configs/mame-libretro/"
#include "/opt/retropie/configs/all/retroarch.cfg"
-
@hhcasey which config is that, the big one with the pastebin? That doesn't look right, are you sure it was BezelProject that made it like that?
-
@sleve_mcdichael
It's for all.
It happens to me everytime I've ever installed BezelProject. -
nine out of time times the issue is because your rom names don't match the bezel names, the bezel project uses no-intro naming format, Cowboy Kid (USA) for example
-
I can go into any libretro core game and F1 into the menu and turn on the overlay.
The overlay shows up and looks great.
If I exit out of the game and start it again, the bezel isn't enabled any longer.I've gone into the BezelProject menu under retropie and enabled bezels for nes, snes, mame, etc.
But, it doesn't seem to be enabling the bezels by default.There's got to be some choice somewhere that I'm not getting right.
-
Why BezelProject loads over 3000 lines to a cfg file is beyond me.
Yeah, that's not supposed to happen.
It happens to me everytime I've ever installed BezelProject.
Mm, not when I've used it in the past, it hasn't, and not when I've tested it just now, it didn't. Did you ever "save configuration" through the RetroArch menu, perhaps? That is one way to make the file like this, and it can lead to these kinds of errors since it overwrites all of the defaults with "hard coded" values. For example:
331. input_overlay_enable = "false"
Your global all config has overlays explicitly disabled, and the local mame config doesn't re-enable them (as it shouldn't need to, because the global one shouldn't do this in the first place and the "default" setting is enabled.)
In any case, you should delete this file and replace it with the
retroarch.cfg.rp-dist
version from the same directory. If you don't have a.rp-dist
, then you can re-install retroarch through the Setup-script to restore the default## Skeleton config file for RetroArch
. Bezels should display after that.Rather than saving in RetroArch, changes to configuration should be made with configuration editor to avoid this problem in the future.
-
@sleve_mcdichael is right - the overlay is not enabled by default. However, this happens now because RetroArch's defaults to 'false' to enable the overlay, whereas in the past the overlays were enabled by default.
RetroPie's configuration for RetroArch enables them, but you probably have reset the configuration and just discarded that. As @sleve_mcdichael said, try not to use the 'save'/'reset' configuration from RetroArch and leave the default configuration as is - either use the configuration editor or a configuration override. Debugging a configuration files that's hundreds of lines is not practical.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.