Problem with 1 legit ps3 controller and not another

edmaul69

I am on retropie 4.4.14

So i have 2 legit ps3 controllers. I have seen over 1000 bootlegs so i am well familiar with differences to say they are legit. When i am in emulationstation it works plugged in and when i go in bluetooth setup with sixaxis driver it doesn’t say anything about unplugging ps3 controller and plugging back in stuff. It used to though. It pops up ps3 controller. Syncs and works fine in everything including emulationstation. Shows up as controller 2.

The other controller if i plug it in while in emulationstation it wont sync or work wired. If i go to setup bluetooth it tells me to do the unplug replug stuff. Syncs fine. Works fine. Once i go back into emulationstation up is a and down is b. Other controls are messed up. If i go back into the linux screens it works fine again. I even re setup my controller in emulationstation no change even though it shows me setting it up correctly. This controller always shows up as controller 7.

Im not sure why one of them is screwed up while in emulationstation.

Efriim

@edmaul69
Do you got the xboxdrv driver enabled, this thing will create virtual controllers. But usually it doesn't make 6 controllers.

edmaul69

@Efriim no I legitimately have 7 controllers hooked up including one ps3 controller. However one always will connect as controller 2 and one will connect as controller 6. But only one ps3 controller at a time. And no i dont have xboxdrv on. My biggest concern is why one of them has screwed up controls only in emulationstation. And why it doesnt work wired in emulationstation. So odd.

Efriim

@edmaul69
Search this file for the matching inconsistencies
\configs\all\emulationstation\es_input.cfg

And try evtest on the /dev/input/event#s for the matching device.

If neither reflect any of the problems, then I would guess it is because there too many controllers for ES binary to parse.

edmaul69

@Efriim ok i just fixed it. Somehow i had an older es_input.cfg that had a lot of controllers i had deleted out before a while back when i found out it had an entry limitation. I never thought about it because it never would accept a controllers settings before if i hit the limit. This one did. But it made it wonky. So i removed all the old no longer owned controllers i had in it and re-set this one up in emulationstation and it is fine. Thanks for reminding me of its limitations even if it wasnt actually the controllers i had hooked up that was the issue.

edmaul69

@Efriim so a question. All ps3 controllers now have their own config entry in emulationstation with separate long as hell guid numbers. For my c64 mini i need to know the guid to set up controllers that arent already configured to manually set one up. Do you know a command i can type to find out a guid #?

edmaul69

@Efriim oh and thank you for the help.

Efriim

@edmaul69
https://askubuntu.com/questions/366994/how-to-identify-game-controller-for-sdl2-in-ubuntu
the second answer obviously.

mitu

@edmaul69 You can re-use the GUID ES assigns in the es_config.cfg - it's per controller model. There's a whole list you can compare and find your controller at https://github.com/gabomdq/SDL_GameControllerDB/blob/master/gamecontrollerdb.txt.

edmaul69

@mitu the problem with the es guid is its only on my ps3 controllers. I will look at all this info to figure out how to get a guid for my dolphinbar. Thanks guys.

Efriim

@edmaul69
~~To take the fun out of what was posted, here is the~~ executable binary that was made from parts of the SDL code. It is explained better in the link.

edmaul69

@Efriim thanks.

edmaul69

This post is deleted!

edmaul69

This post is deleted!

edmaul69

@Efriim ok there is something im not getting. The second answer says compile with

gcc -o sdl2-joystick sdl2-joystick.c `pkg-config ––libs ––cflags sdl2`

Then it says save following as sdl2-joystick.c..... So i stuck this in /home/pi and compiled. Now what?

Efriim

@edmaul69
Save the file sdl2-joystick.c with the c code copied to it. Then compile it with gcc.

edmaul69

@Efriim i did that. I dont know what to do after that to get the guid.

Efriim

@edmaul69
After the code is compiled; with a controller plugged in; run the executable ./sdl2-joystick.

If there is no controller plugged in there won't be any output

edmaul69

@Efriim luckily i dont have to run anything. i found out all the controllers you have plugged in shows their guid in the es_input.cfg file. thanks for all the help.

Efriim

@edmaul69
the output looks like this

050000004c0500006802000000810000 "Sony PLAYSTATION(R)3 Controller" axes:6 buttons:17 hats:0 balls:0

where the first segment is the GUID