RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Ps2 Dual Shock Having to be unplugged and replugged to work once ROM starts

    Scheduled Pinned Locked Moved Help and Support
    4 Posts 1 Posters 603 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • kris964K
      kris964
      last edited by

      I'd like to hello for the first time.

      So I can't seem to find any info on my issue.

      I'm running 3.7 on a Raspberry Pi 3 B. Using a PS2 dual shock with an HDE PS2 to USB converter.

      I can get ES to recognize my controller, by registering the usually method of part start etc.. It's mapped analog (just have to remember to hit the analog button before you start mapping).

      The controller works perfect in ES, but once I get MegaDrive ROM to boot, I'll see the controller being recognized, but none of the buttons work unless I unplug the controller and plug it back in. Then it works fine, including the hotkeys. I've also tried this with a PS1 arcade still, mapped it, and still the same thing. I have to unplug and plug it back in to get it to work with the rom.

      Also, it's plugged into port 0 is seems to move it 1.

      The keyboard works fine without having to be unplugged and plugged back in.

      Any thoughts? Do you think I possible need to use a powered USB hub?

      Thank you for any help you can provide.

      1 Reply Last reply Reply Quote 0
      • kris964K
        kris964
        last edited by

        I think I figured it out, seems I missed a step that has little to no info about it.

        Do you have to edit the main retroarch.cfg folder? Basically add and uncomment the input:

        Joypad buttons.

        Figure these out by using RetroArch-Phoenix or retroarch-joyconfig.

        You can use joypad hats with hnxx, where n is the hat, and xx is a string representing direction.

        E.g. “h0up”

        input_player1_a_btn =

        input_player1_b_btn =

        input_player1_y_btn =

        input_player1_x_btn =

        input_player1_start_btn =

        input_player1_select_btn =

        input_player1_l_btn =

        input_player1_r_btn =

        input_player1_left_btn =

        input_player1_right_btn =

        input_player1_up_btn =

        input_player1_down_btn =

        input_player1_l2_btn =

        input_player1_r2_btn =

        input_player1_l3_btn =

        input_player1_r3_btn =

        etc..

        Add your mapping and uncomment them? None of this is set on my retroarch.cfg which I think is the problem. So it's a step I didn't know about. So basically the when ES maps the controls it's not doing so for retroach correct?

        1 Reply Last reply Reply Quote 0
        • kris964K
          kris964
          last edited by

          Also does anyone have go good map of a PS2 controlled I can use to compare with mine? I mapped mine with the analog button hit, so I could add the dual sticks. Would that be the correct method for a a ps2 controller? Sorry, noob here, I'm a web developer, but this retropie / linux stuff is kinda new to me. Starting to figure out the file structure now.

          1 Reply Last reply Reply Quote 0
          • kris964K
            kris964
            last edited by

            Ok got it to recognize my cono roller, by modifying the retroarch.cfg, but not I'm always forced to be player 2, andon't thus have no hot keys. Ideas?

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

            Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.