Headrush69

2 things: 1) if you use the Ultimarc Servostick app to set it to 8 way before starting LB, does that change anything. 2) if you enable debugging in LEDBlinkyConfig, do you see any messages about setting the Servostick mode in debug.log? If so when?

Curious how your controller is set for your Servostick? Mine is connected to an iPac Ultimate and configured to send keystrokes and it's 8 way in Launchbox. Is your's cofigured as a gamepad? Edit: Checking the LEDBlinky logs, I don't see anywhere where Launchbox passes any information to set the Servostick to 4-way. In LEDBlinkyControlsEditor do you have a default entry? (not for any emulator) If so, in the common section do you have an entry for 8-way?

I believe this is a limitation of XInput. Can you use Dinput instead? (This has limitations as well like both triggers reported on a single axis.)

I think you would have to create specific platforms for each type and create a default lighting for each for this to be automated. (eg Genesis - Single, Genesis - multiplayer) If you turn on debug in LEDBlinky, you can see the information passed from LB to LEDBlinky is fairly simple.

They are in the roms folder in individual folders. (MAME/roms/area51/area51.chd) I thought the same thing as you and have been testing various scenarios to find the cause. If both the zip and CHD are imported, they show up as 2 entries in LB, no <AdditionalApp> entry in the Arcade.xml file. Edit: When importing MAME roms, (not using the Full set import), if you add both the zip file and the CHD file, and you have the Combine roms with the same name option enabled, <AdditionalApplication> entries will be made for both the zip file and the CHD file. I normally don't import CHDs files, but somehow some must have snuck in previously. So this is why CHDs were being deleted.

Thanks, the information I was hoping for. Wouldn't it be better for this dialog to say "Would you like to delete Additional Application app(s) as well?" instead of "Would you like to delete Additional Application ROM(s)?" Definitely something wrong on my system, I have no Additional Apps set for MAME, yet in pruning my rom list I've encountered this dialog many times. I'm going to see I can re-produce it more and find out what is going on. Edit: Did some more testing and inside my Arcade.xml file, there are indeed <AdditionalApplication> entries for some MAME roms. Some point to the CHD, some point to a parent/clone of the same ROM and some are just a repeat of the rom name. So in reality for these entries the CHD was marked as an additional ROM. At this point I have to believe this is related to some corruption I had with my Data/xml platforms files about a year ago. I thought I had cleanly re-imported from scratch everything, but I'm going to re-do and see what happens.

Very odd. I did nothing more than more delete both "Mace" and "Vapor TRX" in LB, was given a dialog about additional ROMs, and both CHDs were deleted from their folders in the MAME rom directory. What's stranger is it doesn't happen for every MAME rom with CHDs. I wonder than if there might be some "corruption/extraneous" info in the Arcade.xml platform file from earlier imports, as I don't have Additional Apps set for any MAME rom. Edit: Re-added these two roms and deleted, and CHDs remain. Something wrong on my end, looking into. Would still like to know what exactly LB is deleting when it says additional ROMs.

I don't believe so. That would be a terrible idea as additional apps you use can apply to many completely different roms. If you deleted for one rom that used that, you could be changing the set up for many other roms/files. I'm pretty sure at least for MAME roms, is additional files means CHDs, but it would be nice to have some exact clarification about what LB looks to delete and/or what files it actually deletes.

On a similar note, when you delete a rom from your collection and you are presented with a dialog asking if you want to delete other associated files, it would be nice to know specifically which file(s) these are. Are there specific rules LB uses to determine which files are being removed? For example, if I delete a MAME rom, is the additional file just the associated CHD file as well, or is a separate BIOS rom also a possibility?

I use MAME for all my Apple II emulation needs. Somewhere in the 0.19x releases of MAME I lost stereo sound for the Mockingboard sound card. It seems the second AY8910 chip doesn't output sound. I had originally found the exact version where AY8910 source changes where made when the problem started, but never got a forum account approved at bannister.org to post or ask about it. The problem exists on both x64 and OS X systems. The weird thing is if I switch from Mockingboard to Phasor (Another sound board that uses the same AY8910 chips, I have normal stero ouput. I have tested on complete clean installs to make sure it isn't a configuration issue. Can anyone test and verify if they have the same issue? Skyfox is a good test as it starts into stereo music without any configuration needed.

Depending on what you need, you might also want to deselect the seperate BIOS files option in ClrMamePro as well, so you have fully independent roms per game.

Ditto. I started with an old arcade cabinet but realized I was going to be spending more time fixing and implementing than getting up and playing. I bought the 27” model as well but heavily modified it for my purposes: made tankstick permanent and completely accessible and add a permanent steering wheel and pedals.

PCem for Win95+ Virtual machine is another option but it depends on your needs and what kind of interface you want.

For post Windows 3.1 games, you could check out PCem. If you google for tutorials there are a couple really good sites with files you will need as well. I set it up a few weeks ago and it was pretty painless, but not something I wanted to keep on my cabinet. (Just didn't mesh well) I stopped at running Win 3.1 games since they fit in, start fast and boot directly into them using DOSBox

What version of LaunchBox are you running? Should be a field in the above for core selection, and one for additional core options. https://imgur.com/a/ZAXImTr

Start MAME, hit Tab key, select Input (General), select User Interface, and right near the top you should see "On Screen Display". See what that is set as and change or erase as needed. I don't want the kids hitting that, so I set it to none. (Hit return, than Esc key)

I just checked OpenEmu on my Mac and it us using MAME 0.149, so it's fairly old in terms of MAME. This does not mean it isn't good, it just might not run some newer games that have been added since. If you are happy with the MAME roms you can play in OpenEmu, you can download MAME 0.149 from mamedev.org and use that version and your current roms will work. If you decide to update, sometimes sites like Pleasuredome don't always work well for some, you can just google for the specific name of the rom you are missing, you'll find a link fairly easily. (as a pure example, if your missing roms for a game, lets say tron.zip and its says you are missing pro0.d2, search for that, not tron.zip. That will usually make sure you get the version you need)

Remove LaunchBox/Data/BigBoxSettings.xml

It's been a while since I've used OpenEMU, but I think the version of MAME included with it was older (.174ish maybe). So checking in MAME first as Viking said is first step. If you find it is a rom issue, you have several options: get an updated MAME set, use an older MAME version,

This won’t get solved unless we narrow down the issue and eliminate possibilities. Two suggestions already given we haven’t heard that you tried: 1) Check permissions on hard drive Directions here 2) Install the previously working version of Launchbox to a NEW location. Do Not copy anything from your previous installation. Start this new copy of LaunchBox, import a few roms. Close and start this same copy of Launchbox, are the previously imported roms there how?

Agreed, it just works. I've tried various Bluetooth options and always stuck with the Mayflash dolphin bar.

You need to set up a dapinput.ini file with the information provided here: Sample dapinput.ini file Keycodes needed For SInge games, I needed a copy of dapinput.ini the main SInge directory, (In Daphne main directory only worked for Daphne games)

I'm actually running without admin privileges on anything with MK version 1.1 and everything works fine, including bananapass. You get a warning about admin privileges, but everything seems fine and they do say to. (Maybe it's a feature I'm not using)

You only have to run Teknoparrot_UI with admin rights, not LaunchBox or BigBox.

Are you 100% sure you aren't using the Retroarch MAME core within Launchbox? If no, 100% sure your command line options for MAME in LaunchBox is not specifying a different mame.ini file?