Controller mapping issue (ES)

This topic contains 1 reply, has 2 voices, and was last updated by  dudleydes 4 years, 10 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #82696


    Hi, I just configured a bluetooth PS3 Controller and it’s working perfectly BUT… everytime I reboot, EmulationStation keeps asking me for a controls remap and I know why. I think it’s because the PS3 Controller takes more time to pair with the BT dongle than ES to start, so it doesn’t see any controller and resets the es_input.cfg file. Am I right?
    How can I avoid it?
    Thank you very much!



    You can get the PS3 controller to connect via Bluetooth without having to configure it in ES everytime by adding a sleep command in the script that launches ES.

    At a command line, run the following:

    cd /usr/bin/
    sudo nano emulationstation

    After the #!/bin/bash line, before the $es_bin, add the command sleep 5.

    My script now looks like:

    sleep 5
    nb_lock_files=$(find /tmp -name ".X?-lock" | wc -l)
    if [ $nb_lock_files -ne 0 ]; then
        echo "X is running. Please shut down X in order to mitigate problems with loosing keyboard input. For example, logout from LXDE$
        exit 1
    $es_bin "$@"

    Save, exit and reboot. When the sixad service has started and the pi doesn’t seem to be doing anything, press the PS button on your controller. When ES has launched you controller should now be working.

    I found 5 seconds was sufficient for the Bluetooth controller to connect. ES for me takes 25 seconds to load so another 5 doesn’t really add much.

Viewing 2 posts - 1 through 2 (of 2 total)

Forums are currently read only - please visit the new RetroPie forums at

We use Cookies and similar technology to collect and analyse information about the users of this website. We use this information to enhance the content, advertising and other services available on the site. Please click ‘Accept cookies’ to consent to the use of this technology by petrockblock. You can manage your preferences at any time by visiting our Cookies Policy page.