Headrush69

Maybe I'm reading too much into your comment, but I wasn't in anyway making any judgement on your responses or your knowledge of the issue. I just thought it might be helpful to point out with that emulator filenames matter and it wasn't a location issue. Are you suggesting I shouldn't have added anything once solved?

There are inconsistencies in the roms pointed to in his/her screenshots. I don't know but, somehow in the process duplicates of the roms were created (the -1 variants) and that's what LB pointed to. Those will never start using m2emulator as it uses game names, not file names. I doubt it was the emulator location that fixed the issue, but looking at the final screen shots you see the games in LB are linked to the correct game names now. Hopefully that's helpful for someone else in the future.

I notice your file name for this rom doesn't match the normal filename. (daytona-1.zip instead of daytona.zip) Are all your filenames like that? Edit: This emulator uses filenames without extensions, to know which game to start, so if named different you will have issues.

I'm trying to understand everything before posting about the issue on MAME Testers site. Maybe you can verify something else I see. When using -gameio joy and going into Configure Inputs (This game), in the gameio section, the button labels are off. For example player one buttons are labelled P2 B1, P2 B2, for player two they are labelled P3 B1, P3 B2, etc. What I find interesting is I would assume the code for this port is the same when using the apple2ee machine, but it displays correctly there.

Are you testing with more than Gauntlet for the IIGS? I can reproduce that issue using standalone MAME with Gauntlet, but other games seem to be fine. Edit: I ran a joystick test program within the MAME using both an analog joystick and the XBOX 360 analog controller, and values are read properly and consistently with a stick center analog value of 128 with no or little to no drift. So I don't think the issue is a dead zone problem but appears more specific to Gauntlet itself with MAME. (This is using -gameio joy slot option) Edit 2: Tried the same Gauntlet image using GSport emulator and no joystick drift.

Just due to the limitations of using LED light sources, I don't think there is a good substitution for black. I started using the colors.ini file but have since customized every MAME game I have in my system. If a game originally had black buttons, I switched to something else. The colors.ini tries to match the original arcade controls, which I think is OK if you have a single game purpose cabinet, but I personally prefer having different colors per action for a multi game cabinet. If 2 buttons are the same color, the user knows they do the same action. This is real handy when you have lots of buttons and want to give the user many options whether left or right handed. Additionally, I keep coin insert and player starts button colors consistent across games.

You need the neogeo.zip bios file as well. Any time you get a message like this from MAME, the filename in the parentheses is telling you the file where it is expecting those files. So just add that set as well.

Best Low Budget low profile GPUs I had a GT 1030 which I started with that was fine for MAME. Only reason I upgraded was to use with emulators for more advanced systems like CEMU,

What are the specs if the Dell? If using MAME is your main focus, single core speed and and SSD are going to give you the best improvement. In MAME games, my NVidia GT 1030 ran games as well as my NVidia 970 GTX, which is much more powerful. If you plan to use some high end shaders, or higher platform emulators like Cemu, Dolphin, etc, than the GPU will become more of a factor.

It could be specific to my system, I don't use fast-forwarding normally, but when I turned off vsync and tested FF in other cores, I didn't have it working on them either. Edit: Needed to turn Threaded Video on and now it works. I searched for that commit again and it was run-ahead, not fast-forwarding, so maybe it does work. Apparently save states do work according to github page.

I don't think it's supported yet. (I remember reading something in one of the commits about an issue when using cycle-exact timings.)

Quite a bit of functionality has been added but I can't speak for how exhaustive it is for all cases. I think their approach is centered on playing games and demos mostly, so Fs-UAE is still valuable. I still use it for running Workbenches. I only have 36 Amiga games and every one runs using this core. A few I needed to be changed from NTSC to PAL and also change the Amiga model emulated. Both these can be done using Retroarch options and saved as a per game config. I believe you can also add to the file name to force model. eg Archon_0903_(A600).lha The one feature I don't see I miss from FS-UAE is warp, which is nice to skip some of those long intros, but since I'm using WHDLOADs, loading times are fast anyways.

You no longer have to do that. I am running WHDLOAD lha archives directly downloaded from the RetroPlay without setting up anything, just need the right kickstart roms in Retroarch/System.

The P-UAE core in Retroarch does both of these right now.

Might want to check out the latest improvements with the P-UAE Retroarch core. I used to use FS-UAE but this Retroarch core is greatly improved lately and supports loading WHDLoad files directly. I only have about 36 Amiga games in WHDLoad format, but they all are running and I gain the features of Retroarch like shaders, remapping, etc. FS-UAE works perfectly, and I still use it for running Workbenches and applications, but P-UAE with Retroarch fits better for games in my cabinet.

Thanks for the clarification. Is this not possible to do manually if you prioritize theme videos in BB, but remove theme videos per platform so they fall back to game play videos for the platforms you want? I wish you could prioritize views based on the absence of media. If I have a game theme video, I want that shown, but if not I'd rather fallback to a different view rather that use a full screen game play video.

Glad you got it going.

You can assign a key to switch between views now.

There could be a number if reasons and we might have to remove device drivers to force it to re-configure. The device is likely labelled as USB Composite Device in Device Manager. I would suggest starting USB Tree View and plugging in the device to find information on it. Device Manager generically labels lots of these devices making it harder to find the proper one.

From the looks of your output, MAME is not seeing the 12in1. The device listed there is your touchpad/keypad combo. I would trying connecting without your hub, and also check out usb tree view to see if it appears there. That adapter is suppose to be driver free, when you connected it originally, did Windows try to configure it?

You can download a free usb tree view like this one USB Tree View to see the devices attached to your system. (Easier than Windows Device Manager) Are you able to post the output from running that mame command?

Is this the adapter to use with a 1-Up arcade controls? Is there an LED on the board and if so is it lit when connected?

Are you sure? Do you have a normal mouse attached to your system, it should at least see that. Is your 12 in 1 recognized in Windows Device Manager?

in your command prompt type cd and then drag your mame folder onto this window. Hit Enter/Return. Then just type