dragon57

@Daliant Sorry, I have been quite sick over the last year and not around here very much. My Nostalgia additions videos can be found on the EmuMovies ftp site under the /Upload Here/_Other/dragon57/Nostalgia path.

There is a native linux build of Emulation Station you could use in the mean time. ETA Prime has a video on it. Hopefully a native LB will arrive one day.

sLpFhaWK, let's take this to another thread, or Personal message so we don't clutter this one.

There is only two things that can cause bezels to not show, rom names not matching the cfg files in the bezel core directories (...\retroarch\config\<core name>), or the core related directory itself in the config directory doesn't exist.

Are you trying to run those systems under MAME, and/or Retroarch?

Yes, sub-directories can be renamed to whatever you want, but be aware the names of the underlying cfg files MUST match the rom names being called, whether in MAME or Retroarch and the sub-directory names themselves must match whatever calling app expects.

Are you referencing odyssey2 bezels under MAME from The Bezel Project? If so, Videopac is the system name configured for our MAME export, not odyssey2.

I use non-merged myself, but that shouldn't matter. When in the MAME Tab/video options section, do you see either of those multi-monitor graphics? If not, look for any existing darius ini files and either delete them, or move them so MAME can't find them, then re-test MAME.

Which Darius game names are you running? The only two multi-monitor bezels included in the MAME pack is darius and darius2. Do you see these in your artwork directory? (See below)

They load fine here. Just like any other bezel file, naming is key. Have you used the Tab key in Mame when one of those games is running, then looked at the video options to see which file MAME is using? You can then go through all the options MAME allows for overlays/backdrops/etc. If you find one option that causes what you want to see, see if you can save a MAME over ride for that one game.

One option is to batch process the files to remove the TV surround.

Not sure what your issue may be. I get no errors when I access and/or download using the Windows app. Could possibly be a temporary issue on Github's end. I would wait a few hours, then retry.

The directory names under your retroarch\configs directory must match the name of the core you are using. There is no duckstation support in our files, so the easiest thing to do is rename your pcsx rearmed sub-directory to match.

Since Nestopia already has a directory for the NES cfg files under retroarch\config\Nestopia, the NES issue must be a naming issue. Even if you have a no-intro rom set, naming standards do change over time. Look in the Nestopia sub-directory and compare the names of those cfg files with your rom names. They names must match 100% except for the suffix (cfg, zip, 7z). For SNES, it appears you will just have to manually set the bezels for those games that don't already have cfg file. Actraiser, for example, only has cfg files for ActRaiser (Japan) (Translated En) and ActRaiser (USA).

OK, so progress. Next step is to figure out why some bezels work and some don't. When no bezels for a core work, generally the problem is the subdirectory name in the retroarch\config directory does not match what the core is expecting. What is the exact core name for NES you are using? For SNES, since some bezels work and some don't, the problem must be a name mismatch between the cfg files for the core under retroarch\config. You mention Actraiser as not working. What is the exact name of the rom?

Thanks for the cfg file. I reviewed it and see no issues with it. A few questions. 1. Is your retroarch installed by the installer version of Retroarch, or a downloaded zip file? 2. How much free space do you have on your c:\ drive? 3. Have you tried to install more than one themed bezel set? Which have you tried? 4. When you run the Bezel app, does the download operation seem to work, or does the app immediately return to the menu after selecting OK to start the install operations?

I assume you have already started Retroarch to see if it runs? If not, do so, and try the bezel app again. If you have run it, attach your retroarch.cfg file here and I'll look at it to see if I can discover anything.

Post a picture of the Retroarch directory. Perhaps it is a non-standard install?

Is the K: drive on a network? If so, make sure the permissions are set correctly so the installer can create the files required.

As far as bezels go, merged and non-merged in and of itself shouldn't matter. Like all other bezels, the names have to match in order for Retroarch to find and show the bezel.

You should be able to update from within the app itself. Make sure betas are enabled in options, then restart the app. It should see and ask for permission to download and install the beta.

Beta 5 installed here. No issues so far. Thanks!

OK, my mobile network must have had an issue earlier. The app was probably silently failing like you mentioned. I just tried it again and it updated. I still have random slow startups. Nothing in the log file. When it starts quick, it is almost instant. When it is slow, it takes between 10-15 seconds. I have a large amount of space on the internal memory. I'm stumped. Running Android 10 on an LG G8.

The last beta I got an email for was beta 2. When was the update code inserted into the betas? Beta 2 isn't seeing any upgrade out there. I made sure I turned on check for beta releases under options, then I restarted the app. Nothing seen. Also, it takes a really long time for the app to start now, and this is with no media or roms imported. I have a totally clean system. Just wondering if anything I am seeing abnormal?

Same.