neither of these things (permissions or starting clean) seemed to resolve. I also @ByteThis did not seem to rectify this by only configuring player 1 (but good idea) With a clean install and remapping all the input settings I am getting to where the select and start button only work in the retropie menu (scrolling diffrent consoles exploring settings etc.... But when I launch a rom NONE of the bottons work.

I ran some more jstest output today....

davis@raspberrypi:~ $ jstest --normal /dev/input**/js0**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

davis@raspberrypi:~ $ jstest --normal /dev/input**/js1**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

So it sees both controllers, but does not detect any button or axis input events. I think It is time to just replace them. Ive had them over a year and the more I think about it the more I think I possibly damaged these things. They used to be mounted in a metal cabinet and the opening I cutout for the control panel was very tight. (see attached called "old") old.jpg

New cabinet.......

new.jpg

I think its time to just replace the usb encoders.

Thank you!!!

@Jdanster said in Raspberry PI Retropie 4.8, first setting, buttons mapping issue (no encoder):

None of the buttons is recognized, any idea why?

Just because you wired the buttons doesn't mean they will automatically work - you'd need a driver to implement an input device based on the GPIO inputs. Something like https://github.com/mholgatem/GPIOnext or https://github.com/recalbox/mk_arcade_joystick_rpi (which is included in RetroPie, in the drivers' section).

If you're just starting up and have limited time and beginner computer skills, I'd recommend you get an USB encoder and use it, instead of wiring the buttons to the GPIOs directly.

@WildDog

If it's for MAME standalone version, In the first post here, do step 10 and 11.

@mitu said in Emulationstation Controller Button Mapping Question...:

Try re-installing it.

That fixed it. Thank you.

@mattsyd said in Setup Difficulties - Hit a Dead End....:

I don't mind which mame system I use. What ever is simpler. Very happy to go with a recommendation.
ON mame I want to setup street fighter ii, mortal combat, frogger, pacman or puckman, space invaders and a few other classics to start with.

I like lr-fbneo; it doesn't even have that TAB-menu and with proper romsets it "just works" in my experience. All control mapping is done by core input remapping in the RetroArch menu.

After wiping the sd card and setting up again, I now have a different issue. The controls on my simple usb gamepad ( ABXY LR and D pad) don't work as mapped in ES. N64 mario cart and puckman on mame are my tests at present. The controller works perfectly for navigating retro pie settings and menus, (and is mapped correctly in es config input menu) until I start playing N64 mario cart for example, all buttons work except the D pad. Can't move left or right.

Does the D-pad work in the (in-game) menus, and just not once the race begins? That's normal; Mario Kart 64 don't use dpad in the race, it need the thumb stick. Dpad work in the menus to select a race but once it start, it need the thumb stick.

I understand it has to be mapped in ES input config, and then again for each emulator too?
Perhaps again for individual games within an emulator too in some cases?

No, when you do it once for ES it should automatically configure inputs both for RetroArch and for the stand-alone emulators at the same time, too.

You can **re-**map the controls for a single game or emulator, but you shouldn't have to set them all up individually.

@Lolonois said in Driver mk_arcade_joystick, multiple MCP23017 and per MCP button mapping?:

Sounds like a doable challenge, but it will take me some time.

You can use the gpio-keys module as an example. In theory, you create an DT fragment and don't write a driver at all, but in this case you need the GPIO to emit gamepad events instead of keyboard events.

@dookieshooter You should delete/rename es_input.cfg and then re-install the emulationstation package, this would generate the correct es_input.cfg file. You'll have to re-configure your controls next time ES boots.

@billymild said in Button mapping not working for lr-parallel-n64:

Is there a way to manually check the ParallelN64 emulator itself? Is there a way to access the retroarch menu from a Keyboard?

Use F1 on the keyboard to open the RetroArch's RGUI menu, then you can check the mappings in the Controller section.

@dankcushions said in Mame button mapping conflicting with Retroarch button mapping:

Input interface - changing it to retropad will mean only your keyboard keys bound to the retropad mapping will work

Not necessarily true. You still have to consider Retropad to core remap. It can nul the input if configured incorrectly.

other mame cores are a mixed bag and probably will only work right if you nul all your retropad bindings for them.

It seems you could just as easily nul the MAME remaps and stick with the Retropad bindings.

the current default of 'simultaneous' is only useful for those who had a keyboard and are using retroarch without any retropad bindings.

Not true at all. I would think the same here for simultaneous, you could nul your MAME maps and use Retropad bindings only. The benefit is if you have a specific game that uses sticks, dials, wheels, paddles, pedals, etc., or whatever is unsupported by Libretro, you'll still have access to the MAME menu to configure it. In addition to the full benefit of the Retropad bindings, keyboard or controller.

Retropad vs. keyboard. Keyboard would be the last one I would choose due to the loss of controller input. You don't necessarily need to configure controller input, if you don't need it, but it's there when you do.

I wouldn't gut the MAME menu until more of the input functionality is ported into the Libretro cores. I agree for the beginner, defaulting the setting to Retropad might make a better OOBE but if you need a particular specialized input, for a favorite game, you'll probably fall back to simultaneous or keyboard to get to the MAME menu.

You could also align the raw and Retropad bindings to avoid "double actions" but you would get sub-optimal layouts on either your control panel or controller.

If you used both, you wouldn't be able to have both set exactly as you want. Take for example a pinball game or like Toobin'. Open on the control panel but fixed on the controller equals terrible button layouts but doing one device or the other would work fine in getting a decent layout.

On cores that don't have those options you can nul one set of inputs or turn on focus mode. I think when Mark added those options if opened up a lot more flexibility that just wasn't possible before and most of us didn't understand the input mechanism at the time and "ghost inputs" as we called them back then.

the standard for fight sticks is

this should get you good defaults in arcade cores, a sensible layout in console cores.

@dankcushions
My bad. Sorry about that and thank you for the guidance. I have reviewed the rules so that I don't make the same mistake again.

@mitu
When I tried using gpionext I kept being met with error messages. I ended up just getting a few different parts to work with the super pi girl drivers. Still, thank you for the help.

@dankcushions Preferably everywhere, because there isn't a huge palm rest area. Having the top row as the main buttons would result in less cramped finger placement.

Thanks for replying, I think I now have a remapping project ahead of me.

@sad_muso said in Slow game loading times with 8bitdo Lite controller:

Out of interest, what is considered the 'best' Bluetooth retro controller all round for Retropie, considering the build quality, input lag and button compatibility with Retropie?

The PS4 DualShock controller is a good Bluetooth controller, no problems pairing and low input lag.

Okay. I was able to fix this by re-installing RetroArch. This doesn't explain what went wrong the first time, but I'm glad I get to enjoy this wonderful emulator now.

Feel free to delete this thread.

Keep up the good work!