@KimDb
hope its not late,I just sign up recently and saw this topic, I have solved this by change this line to
input_map[ui_cancel] keyboard[0,esc] or joystick_button[045e_028e,y] joystick_button[045e_028e,mode]
, for now it can be exit by select + x, I can not figure out why the start button seems can not be detected in this advance mame.

great - thank you!!

@paulr Yeah it's a tough one to navigate. I have the same situation going on and have found nothing so far to help me resolve the issue. Have you found anything?

@MISTERHOLLYW00D great choice, i use AdvanceMame and FBNeo (for NeoGeo) and am very satisfied with this combination.
I also like Nitroball 😊, i recommend to play "Gunball" also. That is the japanese Version of Nitroball which is totally different concerning the Level Design 😉

Update 2:

What a rollercoaster!

So I made some guesses on the joystick ID (above), and got advmame to start long enough to let me map controls. I pulled the trigger, and found it was showing up as j5. I wiggled the gun around, and it showed up as j4. Armed with that knowledge, I went back into advmame-1.4.rc and updated those lines.

Back into duck hunt and... SUCCESS! Sort of. I had movement, and it didn't drift, but it also was clearly moving in 4 directions. Like a joystick.

So I went back to gunconf, set the gun for mouse mode, and went back into AdvMame. Nothing worked (which I expected), but I was able to do that mapping trick and learn that both buttons and movement was showing up as j6. I made the appropriate changes to the rc file, and.. nothing.

Buuuuut, I did learn something about how the rc files works, so I decided to throw caution to the wind and make some changes.

I went back into the rc and set it up this way again:

device_mouse raw device_raw_mousedev[0] /dev/input/mouse0 device_raw_mousedev[1] /dev/input/mouse1 device_raw_mousedev[2] /dev/input/mouse2 device_raw_mousedev[3] /dev/input/mouse3 device_raw_mousetype[0] ps2 device_raw_mousetype[1] ps2 device_raw_mousetype[2] ps2 device_raw_mousetype[3] ps2

I set the lightgun mapping back to "auto", and fired up duckhunt again, and it was a QUALIFIED SUCCESS!

The lightgun is now working (as in, it moves in the right direction at the right time), but there is clearly a calibration and/or sensitivity issue. The gun functions inside a very small area, which I suspect is about the resolution of duckhunt, rather than the resolution of the monitor.

I attempted to calibrate inside of duckhunt, but that's a frustrating experience since the crosshairs bounce all over the place, and I can only guess where I'm supposed to be aiming. Hardly ideal for what I'm trying to make happen here.

I am going to re-calibrate in 4:3 using gunconf, and then play with the sensitivity settings to see if I can get it to match up.

@leitmotiv You can use the same topic, it's up to you if you want to use another forum or not - you might try the AdvanceMAME forums.

@jmbooth2000 Raiden Fighters 2 sound rom was properly dumped for MAME 0.149, so having sound issues with older MAME version is to be expected.

@SpudsMcToole Oh, if it helps - when I get the MESS copyright splash screens and it says "Type OK or move joystick left then right to confirm", the joystick is recognised and works but the keyboard doesn't. (The keyboard works fine with other emulators.)

Was there any resolution to this? I just got a GRS Yoke and the DEADZONE is killing any usability of this.

@pyjamarama Advmame has the config files in /opt/retropie/configs/mame-advmame - see https://retropie.org.uk/docs/MAME/ for each version. For Vice - see the corresponding emulator page at https://retropie.org.uk/docs/Commodore-64-VIC-20-PET/.

Thank you, setting it to SDL worked. I never would have thought to try that.

I think that they modified something in Advmame as it was working prior to one of the updates with 3.x then just nothing and still worked with 1.4 with Alsa.

@alturis said in AdvMAME 3.6 Input Issues with certain games:

but they are nowhere near as convincing as the retroarch crt shaders.

I would probably still be running advmame for everything if it weren’t for those shaders in RetroArch. This and better analog support is the reason lr-mame2003 became my default, but it was mostly for the shaders. Now, Advmame is primarily for vector on my cab until someone adds hi-res rendering to the vector video in 2003.

@alturis

To my knowledge you can't, but I haven't put a lots of time into experimenting either. Acceleration, for example, seems to only affect the max speed. If you continue to test and find out something different, I'd be very interested.

@alturis said in AdvMame Artwork: Missing something:

@jonnykesh Weird. The information I was reading about it seemed to suggest just the opposite. That the old format was .art and the new format was .lay

Yeah, you have it right, but wrong assumptions about which one AdvanceMAME requires. I tried to clarify that here, after @Meneer-Jansen's post.

@andershp ha ha ha ha, must have made an odd typo and then autocorrected to "old". Funny, but possibly true!

@mgrabow said in Tankstick Trackball Not Working in advmame:

verbose mode appears no where the link several people have refered be to.

The option is in the Runcommand menu, but the screenshot/example of that menu is likely old and does not show that choice as an example. However, if you use Runcommand, L "Launch with verbose logging" is an option.

@dudleydes - Have you tried the AdvMAME forums. It might be a long shot but it can't hurt to see if anyone has some suggestions. It sounds like AdvMAME is not doing some cleanup upon exit possibly? AdvMAME Support Forums

I recently bumped up to 3.5 and find it does has some issues that 1.4 doesn't have. I keep both loaded until 3.5 does some "optimizations".