Headrush69

Can you expand on this? Obviously I have to disable the hide console option and startup screens in LB for this to work, but the console log closes so fast it's hard to read. Is there some setting to make it persistent?

I would suggest using standalone MAME over the Retroarch 2015 core, as there have been a ton of changes since that version and MAME's input system is more versatile. (But it all depends on what you're trying to run.) Assuming you're on WIndows 10, right click the Windows icon in taskbar and select Powershell in the menu that appears. type cd following by a space, and than drag your MAME folder onto this screen. Hit return/Enter. This will move you into the MAME directory. Now just type either of those commands from above. Just make sure you have the -v option.

I submitted the error to MameTesters and a fix has already been submitted and checked. So hopefully next MAME version should be fixed. Update: Fix is included in MAME 0.216. Looks like 0.216 introduced a bug (crash) in twincobr though. ?

If you start MAME standalone from a command prompt passing the option -v, it will give you exact details on what the problem is.

I never doubted the number of PD users, just know when doing support best not to assume. It's all good. ☺️ Thanks for posting those.

I think you made some important points which help clarify things, but I wouldn't assume most people get their roms from PD. It doesn't hurt to make sure, as if you're that person that isn't and have issues it could be quite frustrating. The key point here is using the dat file provided by whatever source you are using. All I was trying to point out that might cause problems for people is that if you ClrMamePro with the XML generate from MAME itself, your Non-Merged set will NOT have device files inside rom sets., they will be separate. Of course if you have a full set this is all academic with Launchbox, but if you have a "slim" MAME set, it would matter. MadK9, I'm not a PD member, could you supply a copy of their complete non-merged DAT file? I keep slim sets for different arcade machines I build and that would save a lot of work manually adding these myself.

A user here posted some scripts that made running Phoenix with Launchbox much easier: Works OK but still strange compared to most emulators. For the roms I need, Retroarch core works well enough. For N64 I use Mupen core in Retroarch as well but for any N64 mods, the parallel N64 Retroarch core works when Mupen doesn't. (Kids love Multiplayer Super Mario 64 even though they drive each other crazy with POV issues when they don't work together)

Hardware: https://www.retrorgb.com/mister.html

That would be nice but doesn't sound like it will happen. Since a real non-merged set isn't that popular anyways and even the MAME team don't recommend it, he's not overly interested. Just one of those quirks that could drive someone crazy (yours included), wondering why their non-merged set wasn't working right even when your set looked complete. ?

That's a different argument, It's very likely that the non-merged set on PleasureDome includes the device sets in each rom. The OP said they had a complete merged set already. I'm just trying to point that if they use ClrMamePro (which I believe is the most popular MAME rom manager), to rebuild their set to a Non-Merged set, they will be missing files. To verify, I just rebuilt the set for Galaga from a complete 0.214 set and sure enough namco51 and namco54 device files are not included.

I agree with what you are saying about usefulness but read the last section that is cut off about device sets.... it says you need device sets as well. Originally device sets were considered roms, but that changed at some point with Mame, so they used to be complete sets. From Mame doc you posted “as such You’ll also need the device set as well as any needed for the game” Edit: You can manually add the device sets to game roms, just don’t assume ClrMamePro makes what we use to know as a complete non-merged set.

Are people sure these sets weren’t built with earlier versions of ClrMamePro? According to Roman of ClrMamePro they aren’t included: https://www.emulab.it/forum/index.php?topic=4188.0 Edit: I’m talking about device files, not BIOS files just to be clear.

These do work with the Retroarch flycast core, so you likely have issues with your rom set.

A non-merged set MAY not contain device files either. ClrMAMEPro will not add these to game rom sets. You will have to maintain these yourself. I have a separate DEVICES folder and just add that as a rom path in MAME along with the roms folder.

Thanks for checking. I was hoping to post on MameTester and/or Richard Bannister's MAME forum but can't seem to get a proper account activated. Thankfully using the Phasor option is a work around for now.

No one using MAME for Apple II that can test? It's definetely version 199 where it stops working.

It all depends on the game and the emulator. You have a pretty decent CPU and you probably will have good success with most roms/emus. Some of the newer MAME roms and Switch Emu would likely be helped by overclocking, but you just have to try and see.

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.