@dankcushions it’s about performance. On 2016 I can play eg. Die Hard Arcade with minimal slowdowns during QTE but overall game is pretty playable. With current mame it works in around 10 fps. Apart from that I have Mame2016 romset and don’t need to find another source for that.

It's a pity it doesn't work, it was the ideal steering wheel for an outrun-based arcade, because of the Ferrari logo theme and the license :(

@mahoneyt944 , @Melvin-FoX Thanks for the suggestion, disabling the digital autocenter did the trick!

Thanks pal will do. Cheers
@windg

Had a similar issue with my kidzplay racingwheel.
For that i just mapped the analog control as D-pad without using the "Analog to Digital" option for the individual games i used it with.

Since your controller is broader, you can save the button mapping for entire systems, that do not use analog buttons at all.
Only the systems that do use it you'd still have to do it per game for.

Not really a solution, but its a workable workaround.

Not necessarily - you can remap one of the existing buttons (X/Y/L/R) to be the P2 start. For the games you mentioned, it wouldn't be a problem, since they have very few buttons.

Hey, thanks all. I changed this around as suggested and it worked.

Button 5 is real block and 6 is "quick block".

@keith-f-kelly said in Enhancements for Dialog Navigation/Controls:

I don't see why any button needs to be mapped to the TAB key. TAB doesn't appear to be used anywhere in the menus. Am I missing something?

The physical key Tab is by default mapped to traverse the button selection (in the bottom area) in retropie's dialogs. More generally it is mapped to traverse the input fields/controls of the different widgets available in a dialog.

For 0x0a / 0x0d: I do not stick to 0x0a I just took what was there, maybe it is the cleanest to sent the terminfo's cr instead of 0x0a or 0x0d.

What image are you using?

Okay.

It appears screensaver controls only work with videos - is that right?

Also, while it did initially work setting the screensaver to activate after 5 secs, it decided it didn't like it after a while, and it appears fine with it set back to the minute again. (I'm assuming the GUI not allowing me to go below a minute is something of a warning, here.)

So now my main question really is: has anyone used Skraper recently? It seems great, but try as I might I cannot get the video resizing to work.

Take a look at https://github.com/recalbox/mk_arcade_joystick_rpi, it's similar to what you have in mind and it's already included in RetroPie.

I have the same issue with my Xbox controller. My analog does as you say, but my Dpad works fine.

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

@MBRetrocade said in HELP! Can’t alter MAME2016 controls:

Hello everyone, so all of the sudden I am getting —- in the control input slots in MAME2016 and MAME2003. These are also uneditable. I would really like to get some game controls configured, so any help would be extremely appreciated! Thank you

This is on Retroarch 1.8.5, and I did not see any error messages. I am just unable to change any of my controls suddenly. I also tried re-installing (assuming that I did something) from binary and it did not help. I did not update the system during this.

Here are my
Details:
Raspberry Pi 4B w/4GB ram, 64bit processor
Power Supply used: MODEL DCAR-RSP-3A5C, INPUT 100-240V AC, OUTPUT: 5.1V 3.5A
RetroPie version: Raspbian GNU/Linux 10 (buster) - Linux retropie 4.19.97-v7l+
Built From: RetroPie-Setup version: 4.6.1 (4464b474)
USB Devices connected: SNES controller, USB keyboard
Controller used: SNES controller, USB keyboard

Please note: I did switch to a PS2 USB controller during the process of going through my arcade games & configuring the emulators. It did let me change the controls at first and I did not update anything so I cannot understand why I am suddenly getting three dashes in the input slots - - -

Also note: Mame2003 works up I cannot go up down left or right.

SOLVED, a MAME 2016.rmp file was generated in
configs/arcade/mame2016 and over wrote my controls. I deleted the .rmp file and now I have my controls working again.

Oh, forgot it is a stand-alone, that is true.
I will try to register the analog pad to the d-pad using the script then. Thanks!

@YFZdude I’m also looking at the MAME2016.rmp file (I didn’t change anything in here) but it says

input_libretro_device_p1= “5”
input_libretro_device_p2= “1”
input_libretro_device_p3= “1”
input_libretro_device_p4= “1”
input_libretro_device_p5= “1”
input_player1_analog_dpad_mode = “1”
input_player1_btn_select = “-1”
input_player1_btn_up = “-1”

Is this correct considering select is usually an 8? It doesn’t make sense to me why the select and button up are the same?

Glad it's working for you.
I'm still learning some of this but just for reference, I think a "-1" would be the equivalent of saying that button is either disabled or undefined. All regular buttons probably should have a number with no sign (+ or -) associated with them. An analog function usually mentions an axis and those can have a negative sign for one direction and a positive sign for the other direction.

@roslof - Nice, that looks right, I appreciate the screenshot.

@pjft - Thanks for the tip on AdvMAME I'll give it try this weekend.

@kitdan2332 said in Xinmotek XM-10 not showing 2 controllers:

I've already tried the cmdline thing adding the string of text at the end which I knew wouldn't work. Thoughts?

Apart from that configuration, there's little to do to make it looks like 2 players. Make sure you've put everything on one line in that file. It may also be that the VID:PID combo is different for your encoder. Can you run

cat /proc/bus/input/devices

and post the output here ?