Tempest

@faeran I checked the xml of the new imported games and this is what I've found in each game: <RetroAchievementsHash>COULDNTFILEHASH</RetroAchievementsHash> Thus, I wondered if maybe the problem lies in the new version of the RAHasher. So, I replaced the RAHasher exe in the beta 2 folder with the older one from 13.11. Tested it by importing new games, and it's hashing correctly now. For now, I'll use this old version of RAHasher, and wait for a new update that hopefully will fix it. P.S. One other thing I've noticed by poking around with the "broken" RA hashing import is that after adding a new game, the hash is created at that moment, meaning that refreshing and/or rescanning for achievements will never update the hash; the same thing happens if you just replace the rom in the games folder with another rom with the same name but different hash. You always need to delete the game and import it again. Would it be possible to add a "force hash rescan" option in order to prevent this in the future?

Followed your advice and repaired all Microsoft Visual C++ Redistributable installs. Imported more games and the problem remains. Started a fresh install of 13.12 beta 2 and imported the games. The problem continues. Started a fresh install of 13.11 and imported the games. In this version it works just fine, achievements are hashing correctly. Any thoughts?

Oh ok, it could be that, but it was working fine in the previous version of LB, and never seen this happen before. Anyone had this problem before?

I was testing this new beta version while importing some games and I got an error, i.e. not able to get metadata for one of the games, but I chose to continue the importing process - it was about 30 games for the NES. After the import, the achievements were not detected for those games - and they have the correct hash, I tested them before - even after refreshing and scanning for achievements again. The games that were already in the library were not affected by this. So I decided to test the new feature, removed one single game (without deleting the ROM), and enabled the automated import. The game was detected correctly and imported, but I got a bunch of errors popping up, mostly dll files related to RAhasher.exe - I was able to get one print. So, I moved these last roms from the games folder to a different directory, removed them from LB, restarted LB, and started the import process again. No errors this time, but after the import the games are not recognized as having achievements again - refreshing and scanning for achievements, or even playing them in RetroArch - which normally results in the game being scanned and updated with the achievement badge promptly - did not work. Any thoughts?

Is this the correct folder name for MAME 2003 core after importing Arcade bezels from LB? It created the folder named "MAME 2003 (0" for the config files associated with that specific core. Shouldn't be only MAME 2003? Thanks

When importing bezels using the LB import tool, from what I could tell, it's important that the ROM filename matches the one from the project repository (excluding tags). If that happens, it will import the bezel just fine, including even games that are not part of a No-Intro romset. Example: ROM name "Sonic Classic Heroes (World) (v0.15.03e1) (Sonic 2 Hack)" matched the database name "Sonic Classic Heroes (World) (Hack)". However, when the case doesn't match, it fails to import the bezel completely, or at least that's my diagnostic. Example: ROM name "Sonic The Hedgehog (USA, Europe)" failed to match the data base name "Sonic the Hedgehog (USA, Europe)". Note the "The". It also happened for "Sonic The Hedgehog 2 (World)", "Sonic The Hedgehog 3 (USA)", and some more. I wonder if someone is experiencing the same thing or is it just me? If so, can this be fixed? Thanks

Darn, I was really into this theme. It's one of the best out there, and perfect for my setup. Maybe it will get an update in the future? Oh well, time to look for a new theme. Thanks for the quick reply

I have tried to disable the 3D box model using the new feature starting version 13.1 in Big Box and it works flawlessly in the default theme for game details and coverflow view. However, I just can't seem to make it work in the Unified Redux theme. I unchecked the feature in both main and theme specific options and nothing happens, the 3D box is still there. It looks cool with regular front boxes but not so cool when you use 2.5D boxes, which I do for some platforms. Is there any way to fix this? Maybe I'm missing something... Thanks

The media associated with a game can be the rom name or the title. When the title is changed in LB, the file names of all media are automatically updated. So, if the media has the rom name, it changes to the game title. Is there a way to make LB automatically change all media file names to match game titles?

Hi @faeran, thanks for your reply. The first one I got was on the Sega 32X, After Burner Complete. Then, Blackthorne, also on the Sega 32X. At first I thought it was an issue only related to the Sega 32X metadata, but I've found the same issue also on games for the Sega Genesis. I wonder if someone has noticed this before, maybe in other systems as well. Update: I found more on the Sega 32X. Doom, for example. In the Games DB online there is no double space, but the same description exists in the site TheGamesDB (and it has the double space). Maybe the metadata (description) for some games are still from that site.

Not sure if this is really an issue, but in some games with imported metadata, in the description (under notes), there is a double space normally after a period. It's not a big deal and probably some of you have noticied this already. The thing is that in the Games DB online, for the same game, if you copy paste the same description there is no double space. I'm guessing this is some issue when importing the metadata from the online database.

So I'm using atari800 core in retroarch through Launchbox. Problem is, I use config files per system (i.e. -c config\atari5200.cfg) in order to change overlays, shaders, etc. on multi system cores. However, in this particular core it's different because it saves a config file on root dir (.atari800.cfg) and when I use the command -c config\atari5200.cfg it bypasses the .atari800.cfg file, and the core fails to detect bios paths, etc. Anyone had this problem? Or am I missing something?