Lordmonkus

Yup it's easy enough to do. Setup the Pinballfx.exe as your emulator. Locate your table files which have the extension .pxp, they should be in \Pinball FX2\data_steam\ and then import the table files like any other rom. No special command parameters are needed but you do need to check "Use file name only without file extension" in your Edit Emulator window. Metadata and artwork scraping you may or may not be on your own though, I don't think there is any data for each table in the database.

There aren't any such thing as a "mame bios" as such. There are system bios like for consoles. Any bios that a mame rom needs (such as NeoGeo) goes in the folder with the roms themselves.

Ahh ok, the mayflash adapters I think were problematic, Retroarch couldn't distinguish the controllers connected to it since it was only seeing the mayflash adapter. I believe I read on the forums that is something being worked on and hopefully fixed with the next release.

You can have Launchbox extract the rom before loading it in, but if your zip file has multiple roms inside it may have a problem.

I have multiple controllers hooked up and different controllers setup for different cores working no problem with version 1.3.6 stable release. I use an XBox 360 controller for analog controller games and a Hori pad for non analog. For each core load up and go to the input settings and select the controller you want for that core and then save the per core config with that controller.

MameUIFX is actually no longer in development, there is however a 3rd party UI for Mame simply called Arcade which is its own executable you install to your Mame directory which gives you the exact same look and functionality of MameUIFX. You can find it on EmuCR. Mame as of right now is better that the Retroarch official Mame cores but there are some newer git builds of newer Mame cores that are based on newer builds of Mame which are very good. I still prefer stand alone Mame though.

Look in the Options for controller setup and automation.

I know the stand alone Mednafen supports PAL games but no clue if the Retroarch core does or not.

AntiMicro Portable will let map stuff to it if needed, not sure if it will do exactly what you want though. It's basically a free alternative to Xpadder. https://sourceforge.net/projects/antimicroportable

Nothing I know of for Dreamcast at all unfortunately.

1) Not that I am aware of, not in a simple manner at least but maybe possible in a more complicated manner using some sort of scripting software. 2) None that I know of but it won't hurt to do a quick google search. 3) Yes, it should work with disk images with multiple bin files.

No list that I am aware of but it is a very small list. It will also be easy to tell if compressing to PBP failed because the disk image after will be way too small. The one game I didn't get it to work with was FF VIII.

Another option is to convert your games to PBP format which has some advantages but doesn't work for every game, most games though. But that also can be time consuming depending on how many you have.

The default theme with some tweaks is probably the best in terms of performance. On my lower end older PC turned HTPC I use the default theme with text list (no clear logos), image quality set to medium (still looks decent). Turn off all the animations and only have box art and screen shots showing, no videos. The coverflow views will be slow and sluggish. You will still need some time for the images to cache.

There shouldn't be any problems whatsoever with what you are describing as long as the extra files are just bins. If the other files are audio files then there will most likely be issues. If you want to just for neatness, you can mount the disk image with something like Daemon Tools Lite and re-dump the image using ImgBurn to a cue and single bin file. This will not make any difference in the gameplay and the emulation at all though.

GLupeN64 is in my personal experience the best N64 emulation right now. Project64 is pretty good and so is Mupen64 but GLupeN64 edges it out with better compatibility in my testing and of course your mileage may vary depending on the games you test with. GLupeN64 also supports the GlideN64 plugin texture packs which is a nice bonus. As far as Mame is concerned the git build of the 180 core that Zombeaver linked to is very nice and well worth using but I think I would still stick with the stand alone version of Mame. I certainly would advise using the stand alone Mame over the current official Mame cores in Retroarch.

Talk to Jason about it, he generally doesn't like to do it but I believe he might consider it in the case you are a youtuber or something and want to hide your real name.

Just copying over the update pack files is not recommended at all. You should either download a new full set or use a program such as CLRmamePro to update your set with the update packs. @CriticalCiddid a guide on how to do this.

I'd imagine that the RA core will have the same issues as the stand alone since the core is compiled from the same code. I'm unaware of any changes with WWF Superstars made since 161 but I do know that in the 178 set of Capcom CPS games they now have a .key file which Mame 178 requires.

Retroarch FBA is my choice for NeoGeo, works great and the UniBios is great.

I'm sure you read through this thread but it bears repeating. Abanondon WinKawaks, it's an outdated and difficult to use emulator. You have much better options with Mame, FBA and Retroarch using the FBA core, the emulation quality of all 3 of these options is much better than WinKawaks.

As straight forward as it can be I guess. You get your Retroarch stuff and now you can actually read the "Tab" key menu and change stuff in it like bindings and stuff.

Honestly I have no recommendation for which theme to use since I only use the default theme with text game list. Themes are a personal preference thing and the default really suits my tastes.

From what I have seen setting the bios to UniBios is by default done on the core level and then whether the game is AES vs MVS and its region is saved on a per game level. I also believe this is done internally so you do not actually have to save the settings as a per game setting in RA itself.