@sirhenrythe5th
I think I solved it by disabling display_magnify in the .rc

Please note some games appear to have the wrong aspect. gdarius and gdarius2 seem to be vertical, but videos on youtube appear to show them 4:3. This is unrelated to the setting above I think. I don't know enough about stv games tbh.

@fadangalini

Well that disabled the onboard, but still no audio...
I can only laugh at all the problems I keep getting!

@wjkoontz said in Advmame tab menu not accepting input from any device:

Thanks for helping!

Not sure how I helped :), but glad it's working.

I don't routinely use advmame, but I did a few tests and it looks like - when mapping the input - there is a delay between pressing an input and the corresponding key being displaying in the menu. If I do a simple/single press, nothing is shown, but after the input timeout elapses, the input dialog shows the input has been acknowledged and configured. It's like the UI doesn't update immediately after 1 event processed.
We'll see if something can be done to make the input mapping more responsive.

@mitu
Thanks. That did the trick!

I hadn't thought of configuring the trackball to actually be the spinner.

Both advmame and advmess configuration files are under $HOME/.advnance - named advmame.rc/advmess.rc. Game specific configurations are saved there, prefixed with the game/romset name.

I have a Pi 3b and SI95 runs absolutely horribly in lr-mame2003 and lr-mame2003plus, which is why I was running it in AdvMAME in the first place.

We don't support 3rd party images, especially the ones pre-loaded with ROMs. Ask the seller/scammer that sold you the device.

Hi,
all of them... well the three available for retropie... tried with all of them and there is not a way to change video option beyond the offered by mame itself :( maybe there is an option to edit its reg (i must say i am newbie on raspberry )

That's a good suggestion. I added some notes on persistent device paths.

@mitu thanks again - it worked! it actually worked without the "" surrounding the path of the subfolder (and wouldn't work with the "").

@grant2258 Thanks Grant. I can't understand what's in that link, I'm afraid....beyond my pay-grade. But I'm OK with using the USB keypad to make it work.

@gomisensei said in AdvMame - Looks Pretty, Does Nothing:

@Tango If you set up button1 in input(general) it will work for all games that use the first button. Same with each button, digital axis, analog axis etc that you setup.

You can also set up single unique-per-rom inputs under Inputs(this game) that will not carry over, but will overwrite the general inputs for the rom you set it up in only (not sure about clones).

Cool! Sounds like just what I want.

Thank you.

@andrewsi starting it from gdb inside a ssh session could work to have text mode, unless you tried that. But could be it wont break on correct location either then. Not used gdb that much for such problems

The Pi4 support is currently being worked on, the advmame module is not currently - as-is - compatible with the PI4.

@sirhenrythe5th no reason other than 0.94 was listed on the compatibility chart i linked to and it worked for me. i use lr-mame2000 for most mame games on the GPi (pi zero w).

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.