Headrush69

Try --subsystem neocd Just tested a few games myself but using MAME, think I'll just stick to MVS arcade versions. ? Edit: Reading a thread over at Retroarch mentioned a late 2019 commit made the subsystem option unneeded. Maybe someone that uses this system and emulator for it can confirm? Edit2: The new system for not using the Retroarch subsystem requires setting a core option and also maintaining rom directory in s specific set up.

100% does and thankfully if you need that functionality you can use RocketLauncher with LB for the times you need it. I think adding that functionality to LB just complicates things especially when we have RetroArch handling so many emulation cores and covering the majority of major systems. FanBoy, I use RL just for a few systems for the exact reason you posted. Mostly Teknoparrot games which have notoriously long start up times. (I switched a lot of these games to JConfig which is much faster for many games)

According to the Wikipedia, there are a few exclusives for the NeoGeo CD as well:

That would be a positive for sure than. Comparison of just music differences: Youtube Comparison

From the googling I’ve done on the same subject, indications were the CD variants are more limited than the other versions overall. I tend to only add games that are remarkable different but some like complete libraries of all systems. Which do you like? ? edit: In all fairness, looking back at the articles I saved, comparison was real AES vs Real CD systems. So things like CD loading time not the same issue with emulation.

Edit the said game and within the Emulation tab, set custom command line to use that different emulators commands. for example: To use the FBANeo core instead of the default that was set.

Are these the only controllers you have? Are these wireless?

Sorry, if you install Retroarch from the installer it adds that Start Menu shortcut. Basically just run this from a command prompt in the Retroarch folder:

I don't know for sure, but there could be a possibility of previous device indexes from Retroarch causing issues. Could you temporarily rename your retroarch.cfg to something else to force a default start, and than run Retroarch (log to file) and than post the resulting file? There have been changes to Retroarch because I see from my log it now enumerates Xinput devices as Dinput as well for the purpose of indexing while still being able to use the Xinput drivers for XBOX controllers.

You don't need the entire repo, just click Releases -> Assets and grab the 1.0.3 zip file. (You did get the same files though) Originally i had to install this in the system for Retroarch to work, but somewhere in the line of Retroarch and Windows updates, it works now just placing those files in the Retroarch directory. Edit: Are you sure you are using the correct 32bit or 64bit version that matches Retroarch as well?

Does Windows show the proper resolution or is it doubled vertically?

Retroarch allows you to change the device index and that information is saved in the various overrides. I have found this solution by itself to be insufficient by itself and has changed over Retroarch versions. I use devreorder to set my device order, making sure dynamic devices are last. Then per core or game, whichever I need, set the device index in Retroarch and than save an override. If I put my dynamic devices first, sometimes the order wasn't right, but it could have been specific to my XBOX 360 wireless devices and not always using both at the same time. I just went with the easiest solution for me.

I don't know your set up well enough to say exactly the steps you need but here are some steps. (Other devices you might have for example) 1) Use the link above that DOS76 gave and set up static IDs. 2) Attach all devices and go into MAME and configure as needed. The nice thing is MAME while allow multiple devices to be assigned to a single MAME input. (So for example, Button 1 in MAME inputs settings you can set to a keyboard key and a joystick button) Exit MAME and set the needed cfg file to read only. If it's just general input default.cfg will work or game specific will be the gamename.cfg So now, whether the device is attached when MAME starts or not, both should work and not change. Retroarch is totally different in how it supports devices and is tailored for dynamically attached/de-attached devices. You won't have to do the same thing, but there could be device indexing issues. You'll have to try it as different devices behave differently. Hope that's helpful.

Yes MAME will reset them. This is why you set the file to read only to prevent that. Can you give a little more details on your arcade joysticks? If it's like something with an iPac, the lights are normally controlled via a 3rd party applciation like LEDBlinky and not MAME per sa. Is it just LED lighting that's always on when attached?

I don't know how BB's marquee support works or the mechanism Jason uses to display the marquee, so I can't say if that is grabbing control back after a dual screen MAME game starts, but currently I use a real blunt force AHK script to grab it back. I use the following in the Running AutoHotkey Script section for MAME in LB: Basically it waits for MAME to start, waits 5 seconds (which is long enough on my system), than brings MAME's screen 0 back to front. It will run on every MAME game (not just dual screens), but that doesn't seem to be a problem and I'm sure I could clean it up to wait for the window to lose focus and bring it back rather than using a sleep, but for now it's good enough.

Correct. I don't think there is a specific override for dual screens like there is for vertical.ini, raster.ini, etc. If you have a bunch of dual screen games that use the same driver or system you might be able to override several at once that way. More info here: MAME overrides

Are you making those setting is a specific punchout.ini or the mame.ini? If in mame.ini, it will take control of the second (marquee) screen even if it is not used. So best to place your above options only in punchout.ini. Edit: Just to add to this, on my setup this works OK, but sometimes the main MAME screen looses focus. I believe this is likely related to the BB marquee code, as it's not an issue started from LB. In this case it would probably be fairly easy to use a AutohotKey script to grab the focus back a few seconds after starting.

I don't use save states myself, and I don't think all games support them, or even if MAME can autoload them like Retroarch can, but that about the only way to get around that.

There is something wrong with the artwork file for that game. I don't know where you got your artwork pack, but if you go into MAME directory -> artwork look for a folder or a zip file named exactly the same as your rom. (If you are using the standard MAME locations) If you remove it the problem should be gone, but obviously no artwork. You can re-download artwork for that game from many different sources. You can also inspect the lay file within that folder or zip and see what image file it is pointing to and possibly fix it. Option 1 is likely easier.

1) I assume you are talking the ID within MAME? If so you can look at MAME static IDs for making those IDs static. 2) You'll need to use MAME save states. I'll let someone who know them better to add more, or google that. 3) If your mice are appearing as different IDs, I assume you have enabled multi-mouse in mame.ini. If so you should be able to map your trackball OK within MAME. Have you set Trackball input to use a mouse device in MAME? (are you using command line MAME or a GUI variant?) Setting like this in mame.ini...

I suspect that the command line options you set in LB for MAME are not the same you are using directly with MAME. As Retro808, are you using command line MAME or MAMEUI or another variant?If you are seeing diagonal lines across the screen in MAME, it's like a problem with missing artwork be used by a MAME layout file.

Go into Tools -> Manage Emulators and for the emulator for that system, make sure the path to the emulator exe is correct and that the emulator itself hasn't been moved or deleted.

Probably the easiest work around for the few multi system cores where this might happen.

It saves them in Retroarch -> config -> core as well. So my core override is called Genesis Plus GX.cfg and my directory overrides are called Sega CD.cfg, Sega Genesis.cfg, and Sega MasterSystem.cfg, which match my directory folders holding those roms. The Retroarch configs are additive, so more like appended, so they are incredibly flexible. As you get closer to inidivual game configs, only differences are applied.

I don’t know about stand-alone Mednefan. The Beetle-Saturn core in Retroarch is based on Mednefan and I know it does.