• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
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

mouse as a Zapper lr-fceumm RPi 3 b+

Scheduled Pinned Locked Moved Help and Support
zapperlr-fceummmouseraspberrypi 3b+
52 Posts 9 Posters 9.9k 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.
  • S
    sexbeer @hhromic
    last edited by 24 Nov 2018, 04:52

    @hhromic It did not help

    [INFO] [udev]: Keyboard #0 (/dev/input/event0).
    [ERROR] [udev] Failed to open device: /dev/input/event1 (Success).
    [INFO] [udev]: Mouse #0 (/dev/input/mouse0).
    [INFO] [Joypad]: Found joypad driver: "udev".
    [WARN] [udev]: Full-screen pointer won't be available.
    
    pi@retropie:~ $ ls -la /dev/input/
    total 0
    drwxr-xr-x  4 root root     160 Nov 24 04:34 .
    drwxr-xr-x 15 root root    3340 Nov 24 04:34 ..
    drwxr-xr-x  2 root root     100 Nov 24 04:34 by-id
    drwxr-xr-x  2 root root     100 Nov 24 04:34 by-path
    crw-rw----  1 root input 13, 64 Nov 24 04:34 event0
    crw-rw----  1 root input 13, 65 Nov 24 04:34 event1
    crw-rw----  1 root input 13, 63 Nov 24 04:34 mice
    crw-rw----  1 root input 13, 32 Nov 24 04:34 mouse0
    pi@retropie:~ $ evtest
    No device specified, trying to scan all of /dev/input/event*
    Not running as root, no devices may be available.
    Available devices:
    /dev/input/event0:      MOSART Semi. Rapoo 2.4G Wireless Touch Desktop
    /dev/input/event1:      MOSART Semi. Rapoo 2.4G Wireless Touch Desktop
    Select the device event number [0-1]:
    

    mouse is event1now
    interestingly, the mouse works in the terminal via SSH even when the emulator is running

    H 2 Replies Last reply 12 Dec 2018, 00:03 Reply Quote 0
    • H
      hhromic @sexbeer
      last edited by 12 Dec 2018, 00:03

      @sexbeer finally the issue was identified in RA's side.

      @grant2258 sent a pull request to RetroArch to fix this issue here: https://github.com/libretro/RetroArch/pull/7730
      Once merged your problem should be fixed, keep an eye on that PR @sexbeer ;)

      1 Reply Last reply Reply Quote 1
      • H
        hhromic @sexbeer
        last edited by hhromic 13 Dec 2018, 16:10

        @sexbeer if you feel like trying the patch from @grant2258 , you can do the following while the PRs are in the process of being reviewed/merged:

        cd $HOME/RetroPie-Setup  # go to the RetroPie Setup directory
        sudo ./retropie_packages.sh retroarch clean  # clean the build
        sudo ./retropie_packages.sh retroarch sources  # download the sources
        sudo patch -p1 -d tmp/build/retroarch < <(wget -qO- https://github.com/libretro/RetroArch/pull/7730.diff)  # patch retroarch with PR #7730
        sudo patch -p1 -d tmp/build/retroarch < <(wget -qO- https://github.com/libretro/RetroArch/pull/7759.diff)  # patch retroarch with PR #7759
        sudo ./retropie_packages.sh retroarch build  # build the patched retroarch
        sudo ./retropie_packages.sh retroarch install  # install the patched retroarch
        sudo ./retropie_packages.sh retroarch clean  # to leave all clean again
        

        Afterwards, just launch your game and test if the mouse is now working for you. In particular check that you are not getting this error anymore:

        [ERROR] [udev] Failed to open device: /dev/input/event1 (Success).
        

        Your feedback is highly appreciated! Thanks!

        S 1 Reply Last reply 15 Dec 2018, 20:22 Reply Quote 3
        • S
          sexbeer @hhromic
          last edited by 15 Dec 2018, 20:22

          @hhromic sudo: ./retropie_packages.sh: command not found

          1 Reply Last reply Reply Quote 0
          • G
            grant2258 Banned
            last edited by 15 Dec 2018, 20:29

            type

             cd /home/pi/RetroPie-Setup/
            

            then follow the instructions

            S 1 Reply Last reply 15 Dec 2018, 21:50 Reply Quote 2
            • S
              sexbeer @grant2258
              last edited by 15 Dec 2018, 21:50

              @grant2258 goddammit it works! Hallelujah!

              1 Reply Last reply Reply Quote 2
              • S
                sexbeer
                last edited by 15 Dec 2018, 21:53

                no errors detected

                [INFO] [udev]: Keyboard #0 (/dev/input/event1).
                [INFO] [udev]: Mouse #0 (/dev/input/event2).
                [INFO] [udev]: Mouse #1 (/dev/input/mouse0).
                [INFO] [udev]: Plugged pad: Microsoft X-Box 360 pad (1118:654) on port #0.
                [INFO] [udev]: Pad #0 (/dev/input/event0) supports force feedback.
                [INFO] [udev]: Pad #0 (/dev/input/event0) supports 16 force feedback effects.
                
                H 1 Reply Last reply 15 Dec 2018, 22:06 Reply Quote 1
                • H
                  hhromic @sexbeer
                  last edited by 15 Dec 2018, 22:06

                  @sexbeer yes indeed I forgot to mention that you need to go to the RetroPie directory first! apologies! luckily @grant2258 gave you the hint.

                  and I'm glad your mouse is now working! more points for this patch! thanks for testing. I guess now you can go enjoy some Zapper shooting ;)

                  1 Reply Last reply Reply Quote 1
                  • G
                    grant2258 Banned
                    last edited by 15 Dec 2018, 22:25

                    nice to see hear it working good fot you thanks for posting the results appreciated :)

                    S 1 Reply Last reply 16 Dec 2018, 04:54 Reply Quote 1
                    • S
                      sexbeer @grant2258
                      last edited by 16 Dec 2018, 04:54

                      @grant2258 @hhromic Thanks guys, I'm really happy now :) I hope that this fix will be included in one of the following updates

                      1 Reply Last reply Reply Quote 1
                      • G
                        grant2258 Banned
                        last edited by 17 Dec 2018, 06:40

                        @hhromic good news is the patch is in retroarch now however they asked me to change something which broke it. So i applied another patch to sort it. in your instructions can you add this after the first patch.

                        sudo patch -p1 -d tmp/build/retroarch < <(wget -qO- https://patch-diff.githubusercontent.com/raw/libretro/RetroArch/pull/7759.diff)  # patch retroarch with the PR1
                        
                        H 1 Reply Last reply 17 Dec 2018, 11:54 Reply Quote 1
                        • H
                          hhromic @grant2258
                          last edited by 17 Dec 2018, 11:54

                          @grant2258 great news indeed! I updated my original comment now. I used the same URL formatting as the other PR for consistency.

                          I'm thinking on opening a new topic to direct users to your patch and these instructions, so we can collect more positive feedback and easily direct users having the same issue.

                          G 1 Reply Last reply 17 Dec 2018, 18:23 Reply Quote 1
                          • G
                            grant2258 Banned @hhromic
                            last edited by 17 Dec 2018, 18:23

                            @hhromic sounds like a plan something will need to be in place until retropie decides what to do.

                            1 Reply Last reply Reply Quote 0
                            • M
                              MrRalphMan
                              last edited by MrRalphMan 29 Dec 2018, 17:10

                              @hhromic said in mouse as a Zapper lr-fceumm RPi 3 b+:

                              sudo ./retropie_packages.sh retroarch clean # to leave all clean again

                              Hi,

                              Thank you very much for this, I can now at least use my Wireless KB/Mouse with games such as Missle Command, but I cannot seem to get retroarch to use a different mouse #index and it doesn't matter what I chose in retroarch, once I launch the game it's only the KB's Mouse that works.

                              Many Thanks,

                              Paul

                              *** Update, it works I just rebooted without the Wireless KB Controller in place and it all just worked ***

                              1 Reply Last reply Reply Quote 0
                              • F
                                francis2019
                                last edited by 11 Aug 2019, 13:26

                                Hello
                                I have the same issue with the mouse.
                                I download the last image of retropie and I have the issue. Do you know if the fix is inserted in the new retropie image.
                                When I go to the mame menu in lr-mame2003 I dont have the option " MOUSE X ANALOG" like in the windows version of mame (I use to have an arcade with mame in windows xp)

                                And I dont know where to put mouse-enabled at true. Like we use to do in the mame.ini file.

                                So I tried the command line listed upper in this post, and on the line :
                                sudo patch -p1 -d tmp/build/retroarch < <(wget -qO- https://github.com/libretro/RetroArch/pull/7730.diff)
                                I got and error
                                " Hunk #1 failed at 505 "
                                Any idea.
                                Help need please.

                                1 Reply Last reply Reply Quote 0
                                • G
                                  grant2258 Banned
                                  last edited by 11 Aug 2019, 16:23

                                  Can you post your mame2003 log so we can see what it finds

                                  F 1 Reply Last reply 11 Aug 2019, 20:09 Reply Quote 0
                                  • F
                                    francis2019 @grant2258
                                    last edited by 11 Aug 2019, 20:09

                                    @grant2258 Hello
                                    I chekc on the system and i'm unable to find a mame2003.log
                                    Do you know where it should be.
                                    Also I check the runcommand.log, and tehre is only two lines who said that I launch centipede.
                                    In the mame menu, I cna assign a button to a mouse click. But it cannot register my mouse moving.

                                    Francis

                                    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.

                                      This community forum collects and processes your personal information.
                                      consent.not_received