VodkaParalyzer Posted 7 hours ago Author Posted 7 hours ago 20 minutes ago, dragon57 said: I hate to assume, so all I can do at this point is get some history and maybe some screenshots of your Launchbox emulation setup for the systems you are having problems with. How did the config_nes, config_n64 directories, for example, come from? Are you familiar with the Bezel Project Windows app and if so, have you used it to install bezels for certain systems? If not, I would have to assume you used the now built in bezel installation feature of LaunchBox itself? If so, what version of LaunchBox? In LaunchBox, if you use the Tools/Manage/Emulators action, then select Retroarch and click on the Edit button, you should get an Edit Emulator panel. Click on the Associated Platforms in the left column. You should then get a list of the platforms defined in Retroarch along with there command line parameters. Show us a pic of that. I had stuff setup from nearly a year ago on my current system, but noticed yesterday that a bunch of games were missing their bezels, so I tried selecting all games in LaunchBox and downloading bezels. This didn't solve things. I then remembered using the Bezel Project windows app when I first got back in to emulation on my previous system, so I downloaded the latest version, installed it on my new system, ran it, and selected one by one, the various systems that I was seeing missing bezels. The BP app did its thing. But when I went back to LB to run games, even more were missing their bezels than before. So I started trying to trace things through to see what might be going on and ended up posting here. I'm using 13.25 of LaunchBox Here's RetroArch, as set up in LB And within RetroArch, the Associated Platforms. I added the command line for NES to see if that fixed things. Other than NES, every associated Platform just has -f for its command line. I havn't tried every platform to see how many are no longer showing bezels, but there are a number. The other problem I have here is, the names of my game files don't match what the BP app was looking for. Which is weird, as I didn't have this issue prior to this mess with the same game files. Quote
skizzosjt Posted 7 hours ago Posted 7 hours ago 17 minutes ago, dragon57 said: Correct in all your statements. Overall, a couple items should be noted. 1. The Bezel Project integration written into the LaunchBox application still uses the old, default behavior for Retroarch installation, so you have to pick which way you want your Retroarch structure to be. 2. This isn't to say you can't mix the behaviors. I have a test virtual machine that uses the older default behavior of Retroarch for cores that only support one system which uses the default config directory and the new way of separate, custom cfg files that point to newly created files and directories for those cores that support multiple systems with known overlay issues. It is funny that this way of using custom cfg files that point to system-specific config directories and overlays causes many Windows users of Retroarch some issues of just unfamiliarity. Retropi and many other front ends on Linux have always used this structure, so those users never saw overlay conflicts when using cores that support many consoles/systems. all makes sense now! i'm only using Windows for emulation and had no idea a different OS version of Retroarch structured directories different. not knowing this prior, seeing "_nes" appended on the end looked like a redflag to me 1 Quote
dragon57 Posted 7 hours ago Posted 7 hours ago I suspect the problem of the missing bezels is twofold. 1. The most common issue of a missing bezel is a mismatch in naming of the roms vs the bezel names. The Bezel Project uses the following naming types from their respective databases; No-Intro for consoles, Redump for systems that use optical media, TOSEC for mainly computer type systems, and finally Hyperspin xml data files for systems that may not exist anywhere else. The way to get your naming in sync can be problematic, however we recommand using the Fatmatch utility to rename your roms to match the standard naming used by the various dat files from the naming type mentioned above. 2. The other reason for missing bezels is not specifying which cfg file to use that would have the settings for various bezel related paths/value. Here is an example of a default retroarch installation. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.