Lordmonkus

You can have multiple installs. What is wrong with the look ? Is there graphical glitches or just not looking clean and sharp how ?

A full set will give you all the games in the set minus whatever you decide to filter out in the import process.

Did that fix your issues ?

Yeah, that system should be good enough for Snes9x, it's not a heavy requirements core at all. I would try either a fresh install or removing your retroarch.cfg file temporarily to generate a new default one and testing the core again to see if it still has issues.

I don't know what your system specs are but RA cores do tend to have some slightly higher CPU requirements compared to their stand alone counterparts. But RA offers some stuff that the stand alone versions do not like reduced input and audio latency among other things. It is possible your CPU isn't up to the task or maybe a setting that got changed in RA that is causing you some issues.

You can use pretty much any emulator you want as long as the emulator supports launching via command line, very few emulators do not support this. Like DOS76 said, start with one system and get it working first and move on from there.

That's the only one I know of.

Mednafen and Kronos are not the same an may have different requirements. You may wanna ask over on the Retroarch forums for help, I don't know of anyone here using Kronos at all, we use the Beetle / Mednefen core.

Yup, Jason changed up the reaction emojis.

Version 9.3 - Released January 7, 2018 - Improvement: Daphne emulators should now have "Hide Console Window" checked by default for better compatibility with the startup screens - Fixed: Rare and random null reference error when returning to LaunchBox from games - Fixed: Error when using the list view in LaunchBox and attempting to hide the sidebar - Fixed: Rare but potential null reference error auto-generating child playlists - Fixed: Scan for Added/Removed ROMs error with platforms list's All node selected - Fixed: LaunchBox sidebar counts were updating incorrectly with an active search - Fixed: LaunchBox sidebar counts were sometimes not showing up immediately for All, None, and Exists nodes - Fixed: Big Box was using the LaunchBox startup theme setting instead of the Big Box startup theme setting

There is no simple yes or no answer here, it just depends. Sometimes you can just simply overwrite old exes and files while other times you cannot. It depends on the emulator and whether or not there were any changes made that require a fresh install.

Mess itself is no longer officially being made, it has been merged into Mame, any builds of Mess out there now are made by other people.

I don't think that detection is for game roms but for bios but I also have never used MessUI, I just use the command line version of Mame. In my setup all I have is a separate install of Mame 197 (haven't updated it), in the /roms folder of that install I put all my bios files for console and computer systems I emulate. I then just import the files I need into LB such as roms or cue sheets and they work as long as I have the correct command line parameter set in the associated platforms for that system. Not all systems in the screenshot below are ones I use Mame for though I have tested them and they work.The biggest roadblocks I run into is correct bios and disk images that Mame will accept as working.

Looking at that picture it looks like there are missing files because of the icon (red dot with question mark) and it looks like you have the required files for the NES.

It means it cannot find those files in the bios files that you have.

They just have to be the right bios and good disk images, cue + bin and you load the cue.

Your rom path looks completely messed, there are a few mistakes. First off where you have your bios all you need in your rompath is roms rompath roms Second, you're missing the other bios file; neocdz.zip Third, if your rom path has a space in it it needs to be wrapped in quotes.

I dont know what the Mess_g file is, you should have mess.ini file in the main folder with the mess executable.

Ok, doing some more testing and Port Audio with both WASAPI and Windows WDM-KS they both work through LB with a pa_latency setting of 0.02, going any lower than that resulted in messed up sound. I don't use preview videos in my LB setup to test whether or not that causes any issues at all. I also don't use any frame delay in my setup because I have a G-Sync display but I would imagine using Port Audio with a really low latency setting combined with frame delay would be quite a demanding load on a CPU.

What do you have set for your rompath in your mame.ini file ?

I am using an AMD Ryzen 2700X but I was able to run Port Audio perfectly fine with the settings I posted on my old PC which was an AMD 8350 which is of course slower. While I won't say this wouldn't work but I had troubles even with everything else closed down (including LB) and running just GroovyMame through the command line.

I just spent some time with this trying out the settings posted here and the settings I have posted in my Mame Tutorial: # OSD SOUND OPTIONS # sound portaudio audio_latency 1 # # PORTAUDIO OPTIONS # pa_api "Windows WASAPI" pa_device default pa_latency 0.003334 I had very weird and mixed results. With the settings posted here by @philexile but changing the pa_device to default worked at first but then stopped working. I also tried my settings posted here and it also worked at first but then stopped working. What I get happening is a weird high pitch garbled screeching sound, not fun to listen to so it is trying to make sound. Both settings also stopped working when launching from just the command line outside of Launchbox with Launcbox closed. I really don't know what is going on here. I don't use port audio generally because I like to listen to other sounds from my computer while playing like music or talking to friends in discord while playing.

You can try this playlist file and see if that helps out. Arcade NoFiller.xml