Mouse not working in lr-mame2003

mitu

@frogger1108 We don't support 3rd party images, especially those coming with ROMs. Please try to the image from retropie.org.uk/download and report back.

Frogger1108

@mitu I did. I tried several images as well as the base install, it didn't work with eiter.

wtfbliz

Any progress on this front?

I have exact same issue, and I also have an input where im getting the "Failed to load event X" (success) in the log files.

Anyone?

BuZz

@wtfbliz 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 - no need to bump multiple old threads.

grant2258

Ill clear this up for you the trackball /mouse /analog support isint mapped into mame2003/2003+ properly its a core issue not a retropie/retroarch isssue.

I will be dealing with this in mame2003+ when i get the time. Some improvements have been done in mame2003+ so you can remap analog pedals to buttons ect. Its not complete yet but I will get round to it when time permits.

As far as mame2003 goes you would need to speak to the keepers of that core on fixing this as they are two very seperate cores now code wise

grant2258

there is an option in the mame menu to enable the mouse in options called mouse device try mouse and pointer see how you get on

albecacif

Hi @grant2258 , any luck so far? according to this thread, it is supported now: https://retropie.org.uk/forum/topic/20211/possible-to-modify-trackball-sensitivity-in-retroarch-cfg/6

grant2258

i have no problems using a mouse or touchpad so i would assume it is ok. I havent tried on retropie though i use RA on my laptop and desktop machine. As long as you set your inndex right us shouldnt be an issue

OliB

Maybe this might helps

under:
opt/retropie/configs/all/
edit
retroarch-core-options.cfg

insert:
mame2003-mame_current_mouse_enable = "enabled"

Also the same line for mame2010 and so on....

albecacif

@Frogger1108 said in Mouse not working in lr-mame2003:

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

Hi,
I still get the same error:

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

I tried the evtest command and I get input when I move either the mouse or the trackball.

I also tried with an old image that I had with RP 4.2 and Retroarch 1.6.7. And the trackball works fine with MAME2003 there. Then I upgraded the Retroarch Version to 1.7.X and it stopped working with the same error.

Seems that there is some kind of problem with the 1.7.x RA with mouses and trackball.
thanks

grant2258

download retroarch for windows or linux and try your mouse and trackball there. If it still doesnt work its a RA issue else its a retropie issue

hhromic

there is another user having the exact same issue for NES cores (fceumm and nestopia tested) here: https://retropie.org.uk/forum/topic/20004/mouse-as-a-zapper-lr-fceumm-rpi-3-b/

The error reported [ERROR] [udev] Failed to open device: /dev/input/event1 (Success). is indeed very indicative of a programming bug in RA's input system error handling.
Further debugging is required at RA's level if anyone has the experience/time :) And report back to RA's maintainers.

grant2258

im betting its permissions not being set right issue this command

 sudo usermod -a -G input `whoami`

reboot and try ( i dont think a reboot is requiredjust on the off chance)

 ls -al /dev/input/
total 0
drwxr-xr-x   4 root root     140 Dec  9 18:35 .
drwxr-xr-x  14 root root    3300 Dec  9 18:35 ..
drwxr-xr-x   2 root root      80 Dec  9 18:35 by-id
drwxr-xr-x   2 root root      80 Dec  9 18:35 by-path
crw-rw----+  1 root input 13, 64 Dec  9 18:35 event0
crw-rw----+  1 root input 13,  0 Dec  9 18:35 js0
crw-rw----   1 root input 13, 63 Dec  9 18:35 mice

hhromic

@grant2258 ah good idea! in the other thread I asked the user to check the input devices FILE permissions, and they seemed right.. but didn't think that the current user might not be in the input group. If that is the case then it would be simply a matter of adding the user to the input group. Let's see!

And yes a reboot is not necessary, just re-login the session.

grant2258

i figured saying reboot would be quicker than explaining to a new user to login again either way will work. I didnt even check i just checked my command syntax before posting so I dont know if this is set by default

hhromic

@grant2258 in some older Stretch images I think the input group was forgotten to be set by default, but in recent releases this is corrected and works out of the box. I have installed various stretch images in recent months and they all come with the user correctly configured.

Let's see if the user manages to fix the problem with your suggestion, that would be great news for the other guy on the other thread.

grant2258

well i just checked my standard stretch x64 install the input group isint added there i think this probably is the issue people have been having the good thing is if it is this its so easily fixed on the updated script

hhromic

@grant2258 sorry, I meant Raspbian Stretch for the RPI :)

grant2258

ill install a fresh image rpi and check

hhromic

@grant2258 sure, but no need to install anything, as I said, in recent images it comes correctly configured: https://github.com/RPi-Distro/pi-gen/blob/master/stage2/01-sys-tweaks/01-run.sh#L39