Headrush69

The issue is MAME will reset the controller bindings if it is ever started and the controllers are not online. I don't know what other controllers you have attached to your system, but you might want to look at https://docs.mamedev.org/advanced/devicemap.html and set up mapping so your controller IDs don't change. On my system I map the devices that are always attached first, and then the XBOX wireless controllers as Joy3 and Joy4. Than I config all the control how I want in MAME. NOW, if you start MAME again and the wireless controllers aren't online, they will get reset, so to make sure that doesn't happen, set the default.cfg in the mame cfg folder to read only. If you change specific game bindings you will have to mark each of those as read only as well. If you need to edit these bindings again, make the appropriate files read/write again, and only start MAME once the wireless controllers are online. Reset to read only after making you changes.

Running directly through Mame is always best as it will tell you exactly which file you are missing. Sometimes you can have the rom set, but still be missing a single individual rom within the set.

Are they still working if you start directly with Mame?

Great tool but it doesn't work with XInput devices, just Direct8Input devices. MAME has great input device ordering builtin that you can check out online in the MAME docs which helps for that emulator as well.

This is one of the biggest problems that MAME noobs face, trying to keep a complete MAME rom set and update it with every MAME release. Generally speaking, for most cases there is no need to update MAME and it's rom set with every release. Without going into detailed information, get a set working and don't update unless you need to. (Cases like specific NEW game added, or improvement in a specific driver for one of your games.) For example, the mame_2003_plus core in Retroarch is based on Mame 0.78, yet you'll find it plays the majority of the popular games of the 80s-90s well. If you do want to try to maintain and update romset with every release, a rom manager like ClrMamePro is essential and will do all the hard work of updating your romset without redownloading complete sets.

Start Retroarch. Select Load Core and pick the Genesis Plus GX core. Scroll down to Information in Retroarch and select Core Information If you scroll down it will should show if the proper BIOS is loaded. It's likely you don't have them, These are the files you need: https://docs.libretro.com/library/genesis_plus_gx/ Once you get the ones you need you copy them to your Retroarch/system folder.

Isn't that the truth. I have CCS64, CCS64 in DOS, Hosx64, MAME, WInVice and Retroarch Vice as options for running C64 games. IMHO, when it comes to C64 loading, the Maximum 1541 Speed option in CCS64 is amazing and warp mode in the other emulators doesn't come close. The issue I was having with CCS64 was audio "hiccups". I had almost given up and switched to using WinVice, but found a copy of CCS64 that was compiled differently and it eliminated the major audio hiccups. (There are a lot of CCS64 compiled versions out there; different compilers, release, debug, etc) SID emulation is still better in Vice, but with this version was much improved in CCS64 and what I use. Since I have a custom iPac2 map for my cabinet controls, I have access to the important C64 keys I need. (space, RUN/STOP, F1, F3, F5, F7, Return, Swap Joysticks, Y, N)

Huge difference. The U360 can be used as an analog joystick, or as a general directional stick. In my case I started with just the cheap Happ type joysticks that came in my Xarcade Tankstick. They were terrible for 4-way games, so I upgraded one of the joysticks to a Ultimarc Mag-Stik Plus. This joystick allowed true 4-way/8-way switching and 4-way mode worked great. I didn't find 8-way mode was as good and I had trouble hitting diagonals easily. I then switched to a U360 (with harder spring and restrictor plate), and using downloadable maps was able to get great 8-way, 4-way, and whatever type control I needed. Playing games like Q-bert that required diagonal 4-way worked terrific. Being an analog joystick the throw of the stick was much greater and although I got used to it, the kids didn't like it. Additionally, with how the young kids played, this extra play was fairly rough on the cabinet. Another issue was if I used this joystick in analog mode, it appeared as a joytick and I was having issues with usb device ordering with so many devices connected to my cabinet. (Currently I don't use the gamepad support with the iPac2, and just use the keyboard mapping.) After a lot of googling and reading, I decided to try a true IL Eurostick. Overall much better feel and diagonals work well. The U360 and Mag-Stik Plus are better with 4-way games, but most 4-ways games that matter I run are in MAME and for these I use the Retroarch core mame2003plus which has improved 4-way detection. So far it seems to be working well. A nice feature of leaving the iPac2 in keyboard mode, is for Retroarch cores I can use the cabinet joysticks or the wireless XBox 360 controllers without a need to change any configuration.

I no longer have a U360 in my cabinet. Switched to some authentic IL Eurosticks. For games/emulators that I need true analog input I have Wireless Xbox 360s attached as well. Between the Eurosticks, trackball, Aimtrack lightgun, XBox 360s, and Logotech MOMO steering wheel, seem to everything covered so far.

I know this is a old question, but I'll post my solution in that it might help others. There are several ways of doing this. Launchbox includes pre-run and post,-run AHK scripting tools,Launchbox also allows additional apps to be run before and after each emulator is run. I have had random issues with using these methods and currently if you are using the additional app features, currently Launchbox doesn't let you set this per emulator. You would have to set to each rom/file. (It's been on the feature request vote but hasn't received enough votes.) I find it's much simplier to just create a bat file in the same directory as your emulator and in Launchbox, point the emulator executable to this bat file instead of the emulator exe. (Your bat file will call the emulator executable.) Here is an example of WinVICE.bat I use for loading in a custom iPac2 map for Commodore 64, and restoring the default iPac2 map after the emulator is closed. @echo off call "C:\Program Files (x86)\WinIPAC V2\WinIPAC.exe" "C:\Program Files (x86)\WinIPAC V2\WinVICE.ipc" call C:\Users\ARCADEPC\LaunchBox\Emulators\WinVICE\x64.exe %1 call "C:\Program Files (x86)\WinIPAC V2\WinIPAC.exe" "C:\Program Files (x86)\WinIPAC V2\Default.ipc" exit 0 Obviously you have to create your custom iPac2 maps using WiniPac, (the *.ipc files), but I found this to work flawlessly.

Seems with current versions (1.7.7 here), you need to load a dummy file named cannonball.game Now you set it up just like any other core/rom and things like overrides work as well.

Removed.

I have a dedicated arcade machine with an exit button, so I have not. My GUESS would be, with the Dolphin bar in Mode 4, all the Wii remote buttons are captured by Dolphin itself and mapping to an exit key would not work. Looking in the controller configuration inside of Dolphin, doesn't look like it possible to map buttons outside of the emulation itself. (aka an exit key)

I do the same. Keep a full split set and I have a text file with the names of the roms I want. Each new version of MAME, in the set information panel, import my text file and it will only select the roms I want. Save that dat file and use it to rebuild my non-merged set. So when I needed a set for PI for example, load dat for MAME version 0.78, read my text file, save new dat file. Rebuild my MAME 0.78 set with just the roms I need in non-merged format. So far so good, and haven't needed any roll-back sets or they were in ClrMamePro backup folder.

Just tried here and Wii remotes work fine with Dolphin bar when launched from Big Box. In Big Box, Wii remotes aren't configured and use all controllers is disabled. Are you using standalone Dolphin or the Retroarch core?

Have you run MAME from the command line to see any errors it posts? Most likely some the of BIOS files needed for your MAME version for using Apple IIgs are missing. (They are very picky between MAME versions, but it does work.)

Rename your roms folder to something like roms_old and then create a new roms folder. (in the same directory it was previously) Now in the rebuilder, select split sets and pick the roms_old folder (or whatever you named it) and the source folder and it should rebuild the entire collection you have. If you have a full set, this can be lengthy.

After spending way too much time keeping my name set complete and getting update packs for each version I started using a simpler approach so I spend more time playing MAME than updating it. This method relies on romset names being fairly stable and I'm using a non-merged set and bios included in rom sets. (I include them so BIOSes don't show up when I'm running MAME directly) Like Denzilla, I did the one time approach of manually removing all games I did not want. Even if it was non-working, or my current machine wasn't powerful enough, I included the rom set, so in the future I would have it. Since I used non-merged set, I could be selective on exact version of roms I wanted. (For example, the world version of Double Dragon, ddragonw, not ddragon) Once I had my roms slimmed down, I use a simple BASH command (OS X) or PowerShell command (Windows) to list the rom directory without the extensions) into a text file. So now I have a text file with just the roms I want. (Called Favourites.txt in my case) When a new version of mame comes out, I add it ClrMamePro. I go to the Scanner and Click the Set Info button. In this screen there is an option to load a text file, which we supply the text file created earlier. (Favourites.txt) This will cause only the roms I want to be included. ClrMamePro takes care of the individual roms in each rom set, I don't have to worry if a specific rom was added or deleted with, because I am just filtering by rom set name. It's almost instant, and I can than save a dat from the same window and use this in ClrMamePro. With this my rom set is so much smaller and updating in fairly painless. Every once and a while new files my be added in newer mame versions to game I have, but it is simple to see what I need and a lot easier to find on the internet than getting entire update packs, which are generally 99% for games I don't want. On my PC I have mame version 0.202, but on my Raspberry PI 3, it's only using MAME_2003plus which uses a mame 0.78 romset. No problem, load dat file for mame 0.78 into ClrMamePro, read my favourites.txt file, I can now save a dat for just the games I want that only play with that version of MAME. If your favourites text file has game that was added in a later version of mame, it is simply ignored. ClrMamePro does all the work of selecting the right specific roms for the rom set you want, for that version of mame.

Are you testing a game you have run previously? My guess is that BIOS file is now part of the NEOGEO set, and hence it will fail an audit if not present. However, if you have run the game before, and MAME has saved the specific NEOGEO BIOS you it ran with previously, it will still run since it doesn't need that new BIOS version that was added. As a test, start your game, then go into MAME menu and change the BIOS to that new one. Quit the game and try starting again. It should fail now. (Assuming it will let you pick the newest missing BIOS)

You can put all the update packs in a single folder and just point the rebuilder to that folder and it should work fine.

The new Bluetooth pass-thru option doesn't affect using the Dolphin Bar. The Dolphin Bar however, does NOT support the new Bluetooth option. So you can't use both at the same time. I tried the new Bluetooth pass-thru option using my bluetooth and the only difference I really noticed was the Wii remote speaker sound was now clear instead of the crackled/muffed sound when using the Dolphin Bar. Using that option you can't use the IR part of the Dolphin Bar which you need for some games also. For me, just sticking with the Dolphin Bar is currently the best option. It just works,even easier than the connecting on the Wii itself. It was as simple as selecting the right Mode (4), syncing remotes, and telling Dolphin to use real remotes. Working flawlessly for months now.

How exactly did you update/add the roms? (Directly into your MAME rom directly or using a rom manager) 1) Update packs only have the roms that have been added or changed within a set, not a complete repack of the roms needed for that version of mame. If you just copy the update pack into where your mame roms are, these incomplete updates will often overwrite the set you had before. 2) Launchbox doesn't use the mame.xml. The 'scan for new roms' option just does directory scan if the platform rom directory is properly set. If you want to merge the update packs you need to use a rom manager like ClrMamePro. Technically you could do it manually, but I wouldn't suggest anyone bother unless it was for a few specific roms.

I understand that completely and though I quoted you I was just giving my method in general to anyone. Way back in the day when I started with MacMAME and downloading massive sizes wasn't really an option, I like many MAME users was wasting too much time trying to have a complete an perfect set. I think too many people still do that. Having a compete subset of "my" games was a cleaner option and using the ClrMamePro options above meant I didn't have to worry about the internal specific rom changes within the games I liked. The most important result was the OCD in me was satisfied that the MAME profile in ClrMamePro had a green check mark even though I only had a subset of ROMs.

I only keep a full 0.161 set and each version update pack from then on. (All stored within one directory) What makes things easier is using the Set Information tools within the scanner result window. I have a list of all my favourite MAME roms listed in a text file. (MAME_Favourites.txt) On each new MAME release, I let ClrMamePro read the MAME binary to get the XML information it needs. I do a scan, and from the results page I click the Set Information button. From there you load that text file which will enable only the roms you need for those games. (You don't have to worry about CHDs, or the exact roms needed for the set, it's taken care of automatically.) From the same page, you can now export a dat file for just your mame games. I use this dat file in ClrMamePro with the paths set to where I store the roms for Launchbox. If for some reason it's missing any roms, switch to the rebuilder which has the update pack folder as source and fixed.

You can add both VP9 and VPX as separate platforms and have the best of both worlds.