Logitech F310 Input Issues

markymark52

I recently installed RetroPie and was using the controller with little issue (although retropie would skip R2, the back right trigger, and not bind this specific button) but after successfully solving the input lag issue, key binding has been switched to buttons I didn't assign or do not register in game at all (start became select, select key now doesn't even register, B is binded improperly to A ect.).

I've tried using both Retroarch keybinding and the RetroPie binding when you press start, but none of the changes carries over to the game when I start SNES9x. It seems like its pulling from a different configuration file that's outside of these two binding methods.

Anyone with this gamepad have any similar issues? I looked on google and couldn't find any information about this exact issue.

I'm using a Logitech F310 Gamepad, The controller is set to Direct Input in RetroPie.

mediamogul

@markymark52

It's an unusual problem for sure. When you were having problems mapping the back right trigger, how do you go about solving it? Is it possible that the issue could have originated here in some way? Also, what is the result when mapping the controller in xinput mode?

therantinggeek

Apologies for the late post, but I also have a Logitech F310 gamepad and couldn't get some of my keys to bind properly (nor be recognized at all when attempting to configure it.) I wound up enabling xboxdrv in the RetroPie Setup Script, went back through the controller configuration and got everything to work.

The only two issues I have so far as thus:

RetroPie now thinks there are two controllers connected, instead of just one.
I can't properly exit some of the ROMs by pressing "BACK" (which is mapped to the "SELECT" function) and "START" (mapped to "START") at the same time. So far, this only occurs with Mario Kart 64, and I think it might be an emulator issue. As much as I know to not disconnect the mini-USB power cord from the unit, I can't seem to do anything else.

mediamogul

@therantinggeek said in Logitech F310 Input Issues:

RetroPie now thinks there are two controllers connected, instead of just one.

This is normal. However, I'm currently exploring ways to alleviate any ill effects this can cause. The few problems that arise exist mostly outside of RetroAch where some emulators will access the wrong controller input. Daphne seems to be a notable offender here.

So far, this only occurs with Mario Kart 64, and I think it might be an emulator issue.

What emulator are you using for N64?

therantinggeek

@mediamogul I'm using Mupen64Plus. I'll try using the libretro emulator to see if that makes a difference. If I still can't seem to properly exit a ROM, I may have to do some digging around to find out how to get the button to map (and pull all of the ROMs off my Pi in the meantime). Sad part was, on the original N64 controller there never was an actual "SELECT" button...

As for what I'm going to dub as the "ghost controller" issue, I look forward to the results of your research.

mediamogul

@therantinggeek said in Logitech F310 Input Issues:

As for what I'm going to dub as the "ghost controller" issue, I look forward to the results of your research.

One way or another, it looks like it's going to require a udev rule triggered when the controller is detected.