![]() ![]() ![]() Given the last comment by hunterk, I think there may be an issue with either the placement of the BIOS, or the copies of the BIOS themselves.Īnd yeah, the PC isn’t very old at all. (and I backed up the ROMs I was replacing so I can just copy them back over and overwrite the new ones if I just have to settle for dealing with MAME 2010) I intend to update the entire set once we’ve figured this out. However, when this issue began the very first thing I did was to grab a handful of ROMS that were having the issue from the 244 set in order to see if that was the problem. I cannot remember the exact version, but it was a MAME 2016 set. What version is the romset you are using? I thank you in advance for any help you can provide.Ĭurrent Mame core is 0.244. On the few games that actually load with the current MAME core, this does not happen.Īssistance would be appreciated on both issues if at all possible. ![]() But what is of note here is that the 2010 core is also giving me a weird issue, as when I go into the Retroarch menu and then return to the game, it opens the MAME settings menu, the one opened/closed by pressing Tab on the keyboard, even though NOTHING in my setup is mapped to the Tab key. Why not juse use MAME 2010? Well, in addition to aforementioned handful of uncooperative games, I’m having some other issues with MAME 2010, one of which is of no concern here as it’s clearly an issue with Launchbox. Going back to MAME 2010 most of the games run fine(save for a handful that had previously refused to cooperate with the 2010 core). Games that worked before on the current MAME core no longer function - the games will load, but give me a “files not present” error and not run. I recently updated Retroarch in a (failed) attempt to solve another issue, and I have a whole new issue that’s popped up. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |