meloMini

Maybe you should stop here right now and basically do, what I did. Testing out different emulators. The quickest way in my opinion is to go with retroarch in the first place. If you still want to go with mameui in the long run, you can do this afterwards. So just reread my posts from a few days ago. Setting up retroarch makes you very flexible in the long run. And you can always choose an individual emulator for a specific platform later, when the platform is basically running under retroarch. So invest a little time in setting up retroarch correctly. Then download all mame and fba cores from within retroarch. Make them available through launchbox. And then you are pretty quick in testing out, if there is an issue with the emulator. There are some current turorials form the launchbox team and also from eta prime. Invest about an hour and you should have retroarch up and running.

Sounds like you are pretty new to the topic. Because it has never been easier. It was at least ten time worse / more difficult the last two decades. And this was despite there was always a lot of love, dedication and sofistication in emulation and retro gaming. So to help you out a little. As far as I know until now, your ROM (.zip), bios (.zip) and your CHD (in a seperate folder, named exactly as the rom) go into the same folder. This folder is used by launchbox when importing the game(s). Then you choose retroarch as an emulator. This emulator is the best starting point, because it encompasses a lot of different emulators for the most common platforms. So you have about 6 mame cores (mame emulator versions) and 5 final burn alpha cores already at hand to test your game. So get retroarch running and you should be good to go on your game. Preferred cores would be mame, mame2016, mame2003, fba. Now to versions. CHD version should not be that important. The rom needs to go with the chosen core. So you have to test this out a little. Do you have the correct bios file? If everything is set up correctly, then maybe the bios file isn't the correct one.

Yes, you were right. The CHDs run with mame2016 and the normal mame core. I put the normal mame core now on default for arcade games and registered all mame cores and some fba cores with arcade, so that i can quickly choose between them when starting problematic games. This is very nice and flexible. Should be even quicker to test out from launchbox then from within retroarch. My opinion about placement of the CHD folders is, just to put them inside the roms folder. Because all roms are zipped and all CHDs are in seperate folders, they can be easily selected and moved out of this folder for maintenance purposes. Otherwise they just stay, where they are needed. I try to keep my setup simple. And launchbox in combination with retroarch is the first solution ever, that makes everything really manageable. So a big thank you to everyone involved so far. The level of maturity in 2018 is really awesome.

Hey guys, I'm still a little confused, because I have no reference experience with this topic and don't know, if it's the games/emulator combination or the importing process, why my chd games don't work. I recently imported a non-merged rom set and it worked great using retroarch with the mame2003 core. I then just dropped my chd folders (split, but same mame version) into the same folder as the non-merged rom set. Shouldn't this work just fine? Doesn't the emulator find the needed chd folders the same way as the needed bios files? Or do I really have to reimport the chds somehow?