@southblazia You don't need to install any additional drivers for a DS4, as soon as your pair it via Bluetooth it should be ready to be configured in ES. Please give more information about your setup as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

@saltyy Well i think its no use to try to fix a error that i dont understand, it appers every time even if i reinstall it, and tbh, there a a lot of errors on the pi ^^ and... the error is about a ps3 controller, mine is a ps4 so its kinda wrong ^^

@sonic41092 Well done. Mine has some problems connecting on boot at times. It seems I have to turn on the controller at the right time, otherwise it will connect and I just have to press a button when it says gamepad not found, not a big issue.

@mosi0815 thanks for the reply I will test that out soon. It makes perfect sense to me sounds simple enough. Is echo 1 to enable and echo 0 off? Nvm ill try it out tomorrow if I can.

@ALNiKO I suspect you may have to configure it in EmulationStation as well, but I'm not sure. Using your working controller launch the controller configuration in EmulationStation and see if it's recognized there.

@samforce Can you help me? When I try to do the mount command it says it can't find the file, and when I first boot the Pi up, it says this /bin/sh: 0: can't access tty; job control turned off Does it have something to do with it?

When I have this in rc.local: /usr/local/bin/ds4drv --led 000008 & exit 0 I get this error when booting into the CLI: [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. [ OK ] Started LSB: Start NTP daemon. [error][daemon] 'hcitool clock' returned error. Make sure your bluetooth device is powered up with 'hciconfig hciX up'. [ OK ] Started LSB: start Samba daemons for the AD DC. [ OK ] Started LSB: start Samba NetBIOS nameserver (nmbd). Starting LSB: start Samba SMB/CIFS daemon (smbd)... [ OK ] Started Configure Bluetooth Modems connected by UART. Starting Load/Save RF Kill Switch Status of rfkill1... Starting Bluetooth service... [ OK ] Started Load/Save RF Kill Switch Status of rfkill1. [ OK ] Started Bluetooth service. Try setting your Pi to boot into the CLI and see if you have the same error. It looks to me like something to do with BT isn't initializing in time for the rc.local entry. Does anyone know why this might be and how to rectify it? Thanks

@Noxoreos, never mind on that question regarding the directory (it just looked weird to me; I've never seen a folder with a ".data" at the end). Another question, however, whenever I try and run the shell script, I get an error about not having the permission to access data in the /var/lib/bluetooth/ directory. Any idea what's going on there? and how I might fix it?

No its not with only one emulator Anyone who has a solution? :(

try this...html color codes

Hey @gomisensei today I bought a Sony Dualshock 4 Wireless USB Adapter. It does all the wireless pairing in hardware and appears as a plugged-in USB controller, so you don't need to setup Bluetooth or ds4drv or anything special in software at all. Just plug in, push the adapter for 3 seconds to enter pairing mode, press PS+Select on the controller, and you're good to go. This worked with both my controllers, the one which works over RetroPie Bluetooth menu, and the one which otherwise needs ds4drv. If you have multiple controllers, you need one adapter per controller. I'm going to buy another one soon but I expect it'll work fine. Hope this helps you!