Dualshock controllers on 4.4 with 3B+

[bullethead]

Thanks for this! It worked great after using SSH and creating the rule in Retropie. I did have to reconfigure the controller layout after reboot.

[th0mi]

Hey guys, first: i'm new to the world of retropie, so please be patient:)
I followed the instructions above, but it didnt fixed the problem of the motion sensors.
I looked for the rule, whether it is saved or not.

pi@retropieTU:~ $ sudo cat /etc/udev/rules.d/51-disable-DS3-and-DS4-motion-controls.rules
cat: /etc/udev/rules.d/51-disable-DS3-and-DS4-motion-controls.rules: No such file or directory

So i am wondering why the rule isn't saved. i pressed strg+x, pressed y, then strg+c, strg+x, n
Is the rule saved this way?
Is there any other way to reboot instead?

[mitu]

@th0mi Did you get any error while trying to save the file ? Remember you'll need to run the editor as root, so start it with

sudo nano /etc/udev/rules.d/51-disable-DS3-and-DS4-motion-controls.rules

then enter the text and afterwards save it.

[th0mi]

There wasn't any error. Can't remember the right wording yet, there was something like "File saved at/as..."

I started it with sudo, is there something to else to consider that i run the editor as root?
I am gonna make a screenshot of if in a few minutes.

[th0mi]

screenshot of it

[mitu]

The path looks ok - you can check if the file was created with the command

ls -l /etc/udev/rules.d/51-disable-DS3-and-DS4-motion-controls.rules

Do you have an original Sony DS3/DS4 or something else ? The configuration is specifically for those controllers.

[Madcaplaughs]

I did everything on this post, but my raspberry still recognizes the motion sensor as a device.

[burtthaman]

@Madcaplaughs I can confirm that this works on ps4 dualshock 4.4 internal bluetooth 3B+

If it's not working for you, there's a chance you put the file in the wrong directory. As this is a new file, it would be very easy to think you did it right and create a new file.. but in the wrong place. Again, I am NOT using a dongle. I AM using ps4 controller bluetooth internal. The exact problem in this thread was the issue. Two controllers showed up per controller. And it was exactly this, the motion sensor counted. When I disabled it, everything fixed.

PLEASE make sure you ar using the correct fix as he originally posted the wrong thing. See below

@rsn8887 said in Dualshock controllers on 4.4 with 3B+:

Here are the corrected instructions. I tested this and it works for me. Emulationstation sees only one controller per DS4 and AdvanceMAME does not react to controller motion events anymore.

ssh into your RetroPie

enter

sudo nano /etc/udev/rules.d/51-disable-DS3-and-DS4-motion-controls.rules

paste the following into the editor

#disable DS3/DS4 motion controls
SUBSYSTEM=="input", ATTRS{name}=="*Motion Sensors", RUN+="/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}=""

Hit CTRL-x and y to save

reboot and verify that motion controls are disabled. For example Emulationstation should only detect 1 controller per DS4 etc.

Also, please be sure you have updated your system so we know you're using the same versions/packages as everyone else. Be sure to reconfigure the controller after reboot as well. The button bindings may need to be reset. Lastly, you can use various programs (discussed in other forums) to test your controller keybindings, then compare them to the controller config file. Keep in mind the ps4 bluetooth using internal shows up as "wireless controller" and not dualshock

[youxia]

I ssh using WinSCP. Then I open Terminal. From there I try to execute this line:

sudo nano /etc/udev/rules.d/51-disable-DS3-and-DS4-motion-controls.rule

I get this error: "Command [...] failed with return code 1 and error message: Error opening terminal: unknown.

Any idea what am I doing wrong?

[mitu]

@youxia said in Dualshock controllers on 4.4 with 3B+:

Any idea what am I doing wrong?

The terminal emulator doesn't properly report its name. Try running export TERM=xterm before running the command. If that doesn't work, then use Putty to connect to RetroPie.

And please, don't bump old topics - you should have opened a new one.