Has anyone figured out a solution?

@hophead05
I also have the same problem and same controller. If I change to other n64-emulator the controller works but the emulation is slow.

@herb_fargus

The config for controller mapping in the Reicast config interface asks if you want to map buttons based off of the original controller button names, not the names of the buttons on the controller map located on the Reicast page.

This becomes a problem when the graphic on the Reicast page has a controller map with backwards buttons as you end up mapping buttons backwards. Either the Reicast mapping command prompt should change or the graphic needs to change to reflect the actual buttons. My vote is on the latter. The user must map the controller through the Reicast config prompts as none of the buttons work until you do so.

This is current as of 4.4 stretch.

The Reicast page also states that the controls are automatically configured as of 3.3. This is also false.

Hi!

I'm on retropie with LR-PCX-rearmed emulator and I can not play any games

@deltax5 said in Seggesting a low input lag mode.:

It jumps faster then mame

That says a lot right there. When emulated accurately, 'Metal Slug' will always have a certain amount of slow down like on the original hardware.

@youxia said in Dualshock controllers on 4.4 with 3B+:

Any idea what am I doing wrong?

The terminal emulator doesn't properly report its name. Try running export TERM=xterm before running the command. If that doesn't work, then use Putty to connect to RetroPie.

And please, don't bump old topics - you should have opened a new one.

@mitu Yes

I've had no luck in getting this to work. I think I'm going to go back to the stable system before I tried to get FBA and arcade cheevos working. It's a shame such a small edit can cause such a huge impact. I know my case is special, but there has to be a better fix.

@fuzzybat23 On first install, you will need a keyboard to configure your controller. You can do this by navigating to Options -> Control setup -> Joystick Setup -> Edit Buttons.

Once you have mapped your buttons, the axis mapped to turning will navigate a menu (this has probably already been mapped) and the button mapped to fire will select an item in a menu. I have not found a way to map Escape to a button so a keyboard will be needed to bring up the menu in-game.

I updated the driver via the Retropie-Setup and everythings workung fine. Thanks.

@mitu Thank, that makes sense. I had looked through that link previously multiple times, but not found anything saying that “input_12_btn” didn’t work. I will post my configs tomorrow, and manually modify the cfg file to see what happens. If I can confirm that the “input_12_btn” is being created instead of right trigger or whatever, I will report it as a bug

I know more than 2 years passed, but I wanted my phone to config retropie without using a Keyboard and tested your app. From your code on Github there are 2 problems in the main .py file.
1 - You're importing 2 times subprocess, which is redundant, no big problem whatsoever here
2- There's a Syntax error on line 114 that prevented the service to start on my PI3. There aren't () both at start and end from the print command.
So I changed it, copied the file to /usr/bin/ and it worked like a charm.

@benbaron

FWIW I read on another forum about someone havin the exact same issue with Wii U Pro controllers. They ended up buying a dongle and it resolved the problem.

@mediamogul
thank you, I will try them

@fear_sage42 For donations, follow the link at bottom of the page - https://retropie.org.uk/donate/.

@downup

The closest thing is setting all_users_control_menu = "true". However, this would obviously mean that all users would be able to control the menu and not just player three. However, you could unbind the controller mappings for all RetroArch functions and map them solely as keyboard keys. Then players one and two wouldn't have access from the controllers, but anyone using a keyboard would.

@mitu thank you sir

@BuZz Built in ports work as expected. For anyone else with the issue it's the hub (or the way retroarch handles hubs). Not the end of the world, just would have been nice as the ports are numbered 1-5 for those to match up with the players. I may try 2 of the same controller now to see how that affects it.

To follow up, I purchased a Logitech F710 tonight, and what I’ve discovered is that the issue seems to be related to xinput generally. When I switched xinput off for the 710, everything suddenly worked as it should. Previously, both controllers on xinput had another issue I forgot to mention above, which was when I did the controller button configuration process, things went wonky when I got to the triggers.

Pressing the triggers would actuate twice, or sometimes not at all, forcing me to restart the config process. Switching the Logitech off of xinput fixed this issue as well as the lag/freezing problem. Obviously for now, my issue is resolved, strangely by doing the opposite of what the wiki tells me. It would be nice to be able to make xinput work properly, but unless and until that happens, I do at least have a working controller.

@dash-dot I bought the adapter because for the life of me, I couldn't get my controllers paired with the bluetooth on my pi. I tried everything. Some people have had luck pairing them, but unfortunately I was one person who couldn't get the generic ones to connect. I leave my pi in one place all the time, so I don't mind having the adapter at all as long as my controllers work ! :-)

EDIT: I didn't have to calibrate anything. Plugged the adapter in and synced my first controller and the other ones followed suit just by turning the controllers themselves on. No other messing around with them ! I bought this adapter as I was new to the scene at that time and didn't know what other dongles existed for the controllers to function.