Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RetroArch 1.0.0.3 on Ubuntu 15.04 64bit: Xbox 360 wireless controller crashes RetrochArch #1727

Closed
melo0187 opened this issue May 27, 2015 · 11 comments

Comments

@melo0187
Copy link

Hey there,

I installed RetroArch 1.0.0.3 from the official stable ppa on Ubuntu 15.04 64bit. My Xbox 360 wireless controller (using xboxdrv) is being detected and I can bind all keys in rgui. However after binding the keys, things get strange. I can start navigating around rgui with the controller, but not as expected. The button on the right for example enters a menu entry instead of going up one menu. Also pressing the button on the left reproducibly crashes (or maybe just quits?) both rgui and RetroArch cores (tested with snes9x_libretro.so).

No matter what input/joystick driver I choose or whether I use just Retropad or Retropad w/ analog, the problem with messed up mapping and crashing/quitting the entire thing by pushing the left button persists.

I switched log_verbosity to true in retroarch.cfg and run retroarch from terminal. There are several outputs, few errors which seem to be handled by fallbacks, but nothing obviously related to the problem.
Find the output in this gist: https://gist.github.com/melo0187/ef0a030be46d18bb25c3

I believe my controller and the xboxdrv setup is fine, since it works in Steam Big Picture and several Steam games, EmulationStation and Dolphin-Emu.

Any help is much appreciated and I would be glad to provide further information to help fix this.

@sergiobenrocha2
Copy link
Contributor

It's a known issue, take a look at libretro/retroarch-joypad-autoconfig#38

RetroArch thinks it's another joypad, which already has a config file.

@melo0187
Copy link
Author

@sergiobenrocha2 Thanks for the reply.
So I read issue libretro/retroarch-joypad-autoconfig#38, but I'm not sure if I understand correctly. From what I got it seems there is no solution to this problem yet or did I just misinterpret what your wrote in libretro/retroarch-joypad-autoconfig#38? I have a wireless receiver and 1 wireless xbox 360 controller and would be glad to test and help however I can to get this working.

@sergiobenrocha2
Copy link
Contributor

Man, don't reference another issue in this one...

The issue is that retroarch doesn't know to differentiate your receiver from another one. I already tried here, it's a mess.

@melo0187
Copy link
Author

Sorry, for referencing the wrong issue. I did correct the references.

So there is no solution to this problem apparently... pitty.

@sergiobenrocha2
Copy link
Contributor

There is, config it yourself on Settings --> Input Settings

@melo0187
Copy link
Author

melo0187 commented Jun 1, 2015

But that is what I did!
I start RetroArch/rgui, go to Settings --> Input Settings, bind everything for my controller, which seems to work fine, but after binding things get weird. The bottom button gets me up one menu hierarchy instead of entering a menu, the right button enters the highlighted menu entry and the left button just crashes/quits retroarch...

@andres-asm
Copy link
Contributor

Reopen this if it's still an issue

@ghost
Copy link

ghost commented Jan 15, 2016

Unresponsive on Linux Mint 17.3. Keyboard is desactived when the controller is connected. This controller works fine with all other emulators.

@sergiobenrocha2
Copy link
Contributor

I don't know what you guys are doing, it's working here (kernel 3.13). Are you using the xboxdrv? Don't use that, you don't need it.

@ghost
Copy link

ghost commented Jan 17, 2016

I didn't know that. Works fine now. It is probably difficult to obtain this information, in particular when English is not your native language. So, thank you very much for your answer that was very helpful.

@andres-asm
Copy link
Contributor

the problem might be if you're still on 1.0.0.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants