I got it for my emulators, (Mupen64plus, ZSNES, Gens) and it just worked. I recently purchased this same gamepad and it worked as soon as I plugged it in. If software, any ideas how to fix this? Thanks. Is this a hardware or software problem? I don't have any other systems to test the controller on. Dual Action Gamepadīus 001 Device 002: ID 046d:0a0c Logitech, Inc. Then, when I run jscalibrator or jscal or jstest the controller will show up, but it will not recognize input - everything stays at zero no matter what button(s) I press.īus 001 Device 010: ID 046d:c216 Logitech, Inc. When I set my controller to "X" it does not show up in dev/input and jscalibrator says it could not access the specified paths, but if I unplug it, set it to "D", and plug it back in it will show up as dev/input/js0. Is this normal, or some sort of hardware failure? When I set my Logitech controller to "X" (Xinput), pushing the mode button will make the green light come on, but when setting it to "D" (DirectInput) the light turns off and will not come on when pressed. Thanks for your help and pointers, it's really appreciated a lot.I have a Gigaware USB Controller (Radioshack brand), and that works perfectly, but I can't get my new Logitech F310 USB gamepad to work. I guess I will just accept that my F310 is broken (or incompatible with Recalbox) and will just stick to the Xbox 360 one, but if anyone has any further ideas, please let me know. I disabled the PS3 one and enabled the Xbox one, and that makes the Xbox controller work perfectly. Then I checked this thread and it suggests to edit nf. This same method doesn't work for the F310 though. That's like "activating" it, and then it all works. So I noticed that with the Xbox controller, no button presses get detected within any games either.UNTIL I press the left shoulder button. If I set the F310 to "X", it does get detected in ES. Even when I use the virtual gamepad or another controller (I got an Xbox 360 controller today), the F310 just doesn't get detected in any way when it's set to "D". So.long story: no, when the F310 is in Direct mode, I can not navigate use it at all. an Xbox 360 controller works, but only after making a small adjustment in nf.In "X" mode, it works in ES, but not in any games in "D" mode, the F310 does nothing, anywhere, ever.I'm also considering to just get a second hand Xbox 360 controller, since that seems to work out of the box for everyone, but if I can get my F310 to work, I won't try that. I hate asking this (because I have the feeling I'm missing something very simple, and as a newbie I'm scared that someone will point me to a post/article where this exact issue is explained), but any help would be appreciated. It only works when it's set to X the moment I boot up and don't change it anymore. I did try switching from X to D on the back, but when it's on D, it doesn't respond at all anymore, not even in the Recalbox menu. The only way to get out of it again is to hit ESC on my keyboard. I tried many games, many systems (GB, GBA, NES, SNES, MAME), but I can't get any game to start, no response when I press any button on the F310. However, the controller doesn't do anything at all when I'm in a game. When I configure the controller, I do have some issues with the L2/R2 buttons (same as reported here: ) but I can still use it without any problems. I have a new Pi with Recalbox 4.0.0 and when my Logitech F310 is plugged in, I can use it to control the main Recalbox menus and everything.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |