Retropie Controller Stops Working When Plugged in Again
Hello at that place!
I accept recently finished to build a RetroPie setup. The main intend was to use information technology with my original N64 controllers and for testing I have setup four xbox controllers via the usb receiver.
And so far so good. Everything is working now (it was a really hard time to become this done only it finally worked out) which ways: 4 N64 controllers hooked up that are simply used when emulating N64 games and for all other cores, xbox controllers are used.
At present to the problem.
Equally I have various Playstation i to 4 controllers laying around here, I would like to use those with retroarch.
Setting up the playstation controllers work.
I.E:
-setting upwards ps1 controllers via three different usb converters piece of work.
-setting up ps3 controllers via usb cablevision and bluetooth work.
-setting up ps4 controllers via usb cable and bluetooth piece of work.
"work" ways that they are recognised in Emulationstation and I can utilize them to navigate in the menu.
They as well appear in retroarch if I can manage to go into the menu.
BUT:
as soon as I try to launch any emulator or even the Retroarch menu through retropie, Retroarch crashes to emulationstation. It starts normally as before long as I remove whatsoever playstation controller (pull the cablevision/adapter or turn off the controller).
When I start retroarch with no Playstation controller and plug information technology in afterwards, I tin can assign the PS controller to player1 and start playing. Information technology is so but impossible to open up the retroarch menu or go out a game. Whatsoever other input device then stops to piece of work. even the keyboard.
When I look into the libretro log, it leads to a runcommand error that only gives a line where it writes the error to the log. So this is not very helpful.
I am running retropie on a raspberry pi 3b+.
If anyone has an idea how to solve this I would be very happy ^^
@KrtschMaster said in retroarch crashing when connecting any new controller:
When I look into the libretro log, it leads to a runcommand error that only gives a line where information technology writes the fault to the log. Then this is not very helpful.
You need to enable Verbose Logging in the Runcommand launch menu to get a better log in /dev/shm/runcommand.log
. Can you please add more info about your release/system - https://retropie.org.uk/forum/topic/3/read-this-outset.
the Pi is a 3b+
powersupply is a Huawei supercharger 5V/4.5A
RetroPie Version: Merge a161774a 0311a953 (just thing close to version i could find)
Retroarch Git version: 9750719
MicroSD: 128 Gb SanDisk Ultra
build from: "retropie-4.4-rpi2_rpi3.img" from https://retropie.org.uk/download/
connected usb devices: Microsoft xbox360 wireless receiver. Sometimes Ruby K-224 keyboard
COntroller used: Xbox360 wireless controller, Playstation1,2,3,4 controller with and without analog, with cable and with bluetooth.
Verbose logging is not possible equally I tin't launch the runcommand menu.
Runcommand log: https://pastebin.com/z9bsQMhK
@KrtschMaster said in retroarch crashing when connecting any new controller:
RetroPie Version: Merge a161774a 0311a953 (only matter close to version i could find)
The RetroPie version is shown at the superlative of the screen when you open the setup script (you lot seem to have a recent version).
Retroarch Git version: 9750719
If yous open the RGUI, you'll see the RetroArch version at the lesser of the menu
Verbose logging is not possible equally I can't launch the runcommand card.
Did you disable the Runcommand menu ? It's enabled by default - https://retropie.org.united kingdom of great britain and northern ireland/docs/Runcommand/#runcommand-launch-menu ?
Is the problem but with PS1 games or also with other games ?
Thanks.
So retroarch version is 1.7.6
retropie version is four.4.9
the dialog is turned on and when i utilise the xbox controllers with ps controllers not plugged in, it starts fine. But with plugged in PS controllers it does not even get to the launch screen.
The problem is with every emulator that uses retroarch. I deceit fifty-fifty launch the menu entry "Retroarch" from within emulationstation.
@KrtschMaster Update your RetroPie-Setup script, there have been some improvements w.r.t. Runcommand and gamepads in the terminal ii weeks, and so this might fix the Runcommand not appearing.
Tin you become a list of your gamepads with cat /proc/bus/input/devices
and show them in a code block here in the topic ?
i'one thousand currently bankroll up the working sd menu. this takes a while. then i'll poste the inputs and endeavour the update. if my memory is correct, at that place was an error when i wanted to update the setupscript concluding fourth dimension. simply this could have been some weeks ago. I'll try once more.
I come up back hither when everything is done, requite me some hours. ^^
Thank you and then far.
Well at present, I did the update (basic packages/update all) the runcommand launch screen is now visible and I selected launch with verbose. The error message is still the same. -> https://pastebin.com/Z1mjF0Zf
Here is the proc/bus/input/devices output: https://pastebin.com/bSEnBtW9
I volition now endeavor to set everything upward with a fresh image.
I have at present installed retropie from scratch. It is not updated in any manner, simply the image from retropie.org.
I accept set i ps4 via bluetooth and two ps1 controllers via usb adapter. Right now it works fine. I doubtable the xbox receiver to interfere with the other controllers. when i had the ps3 controller setup and on and turned on an xbox controller, it took the nex available index (LED on the xbox logo.)
I will do some testing and study back. but i think i volition stick with the fresh prototype and go on from here.
@KrtschMaster I'd suggest to update to latest version before installing any drivers and use the sixaxis
driver instead of the ps3controller
commuter. Also, you lot don't need to install xboxdrv
, it'due south not an actual Xbox driver - but an userspace driver simulating an Xbox controller. For Xbox wired controllers, the driver used is xpad
, which I advise re-installing subsequently y'all update everything (OS + RetroPie packages and script).
I think your trouble comes from the xboxdrv
, which interferes with normal controller operations. Your RetroArch log is nevertheless not fix to verbose, to cheque what controllers it detects.
Afterwards the fresh install yesterday I setup one ps4 bt controller and ii PS1 wird controllers. No changes done to the xbox stuff.
Tested with PS1 game and everything worked groovy (emulator started up)
So i did all Updates, nothing works.
I will try updating all packages 1 past 1 and run into which one breaks Thema Controller Setup.
@KrtschMaster The updates to OS (Linux kernel) volition change the drivers - the Sony drivers for PS3/4 controllers will change their mappings with the kernel update. That'southward why I recommended to practice any updates before mapping your controllers.
Hullo.
I have now used another sd carte with a fresh new image. Did all updates as presently every bit I could, before configuring whatever inputs. It took almost 3 hours and finished with some warnings on emulationstation. But nothing wild.
I have then put a psx rom onto the pi and configured ane ps1 controller via usb adapter and i ps4 controller via bluetooth.
Everithing seems to work fine right now. I am going to add together the n64 controllers and some more cores. But for at present: Cheers very much @mitu for your support.
Source: https://retropie.org.uk/forum/topic/21738/retroarch-crashing-when-connecting-any-new-controller
0 Response to "Retropie Controller Stops Working When Plugged in Again"
Post a Comment