RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login

    NES controller not working with New ControlBlock2 build

    Scheduled Pinned Locked Moved ControlBlock, PowerBlock & Co.
    nescontrolblock2newbie question
    25 Posts 6 Posters 4.1k 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.
    • NeoKnuxN
      NeoKnux
      last edited by

      I am having the EXACT same issue as Herzog.
      I actually performed the exact same tests as well before checking this thread, and had the exact same results.

      1 Reply Last reply Reply Quote 0
      • P
        petrockblog Global Moderator
        last edited by

        There was a bug with a recently added additional virtual keyboard button, which is fixed now (finally). Sorry for this bug!

        You can attach any momentary buttons on Player 1 A or B. Pressing the buttons will lead to a simulated press of the ESC or the F1 key.

        1 Reply Last reply Reply Quote 0
        • H
          Herzog Leto
          last edited by Herzog Leto

          Thanks for your fast response! I will test it the next few days.

          1 Reply Last reply Reply Quote 0
          • NeoKnuxN
            NeoKnux
            last edited by

            Thank you for the amazing turn around time! I reinstalled the driver, and everything is working perfect again.

            1 Reply Last reply Reply Quote 0
            • S
              SuperPitendo
              last edited by

              Nope...
              After reinstallation of the driver I still have the same problem like Hravnkel.
              Setting: RPI 3b+, 4.4 Image, Controlblock2, SNES Controller.
              Gamepadtype is configured as "snes".
              The powerswitch function works well but if I want to configure the input just the "B" button is recognized...

              1 Reply Last reply Reply Quote 0
              • P
                petrockblog Global Moderator
                last edited by

                Ok, I was able to reproduce your observation with NES controllers. I have fixed it a few minutes ago.

                There is now a dedicated NES gamepad type in the configuration: Use "nes" as gamepad type in /etc/controlblockconfig.cfg.

                1 Reply Last reply Reply Quote 0
                • H
                  Herzog Leto
                  last edited by

                  My problems are also gone. Thanks a lot!
                  By the way, this time I used the Retropie-setup script to install the driver. Works fine.

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sledrunner21
                    last edited by

                    Original poster here.

                    I was able to install the latest driver using:
                    wget -O - https://raw.githubusercontent.com/petrockblog/ControlBlockService2/master/install.sh | sudo bash

                    I took me a while to understand the difference between US & UK keyboards to make the "|" (pipe) symbol. For those w/ US keyboards, use the lower right ALT + "~" (next to #1).

                    I am struggling again w/ having and empty /ect/controlblockconfig.cfg file which is preventing me from setting the controller as NES or SNES.
                    cd ControlBlockService2
                    sudo nano /ect/controlblockconfig.cfg

                    I can run jstest /dev/input/js0 and it shows driver 2.1.0 (same as before) and being set as arcade (I had switched it to SNES w/ the old driver back when I could open the config file).

                    How do I get the /ect/controlblockconfig.cfg file to open again so I can edit it to NES now?

                    1 Reply Last reply Reply Quote 0
                    • P
                      petrockblog Global Moderator
                      last edited by

                      You can restore the original configuration file by running the install script again, e.g., by running sudo ./install.sh from within the ControlBlockService2 directory.

                      1 Reply Last reply Reply Quote 0
                      • P
                        petrockblog Global Moderator
                        last edited by

                        Also, the config file is located in the folder supplementary within the driver folder ControlBlockService2.

                        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.