Trackball not working 4.4, retroarch 1.7.3

gottfired

Hi,

I'm having trouble getting my trackball to work with retropie 4.4 and retroarch 1.7.3. Same setup (3B+, trackball, mame 2003) worked fine with retroarch 1.5.0

HW: Pi 3B+

Game tried: Marble Madness on lr-mame2003

I've followed the steps from https://retropie.org.uk/docs/Spinners,-Trackballs,-Lightguns,-and-other-Mouse-Devices/

cat /dev/input/mouse0 confirms the trackball is working.
input driver is udev
input_player1_mouse_index = "0" is set in retroarch.cfg
but in my runcommand.log I get the following error

[INFO] [udev]: Keyboard #0 (/dev/input/event0).
[ERROR] [udev] Failed to open device: /dev/input/event2 (Success).
[INFO] [udev]: Mouse #0 (/dev/input/mouse0).
[INFO] [udev]: Plugged pad: Twin USB Joystick (2064:1) on port #0.
[INFO] [udev]: Pad #0 (/dev/input/event3) supports 0 force feedback effects.

I also tried to use mouse index 2, but that also didn't work.

So I think I've exhausted all options. Is there anything I might have missed?

gottfired

@gottfired I fixed this by using AdvanceMame.

Libretro cores don't recognize my trackball anymore in 4.4. Hope this gets fixed in the future. It used to work fine.

edmaul69

@gottfired did you try mouse index 1? So in the new retroarch every mouse device is separated hence the mouse index number. So keyboards controllers and other devices can be seen as a mouse. My keyboard is seen as keyboard/mouse/joystick. My 2600-daptor is seen as a mouse. My dolphinbar is seen as 4 mice. And i have a mouse. So you are best trying mouse index 0-9 until you hopefully find the right one for your trackball.

gottfired

@edmaul69 yes, I tried mouse index 0 to 4, just to make sure.

wtfbliz

Any updates? Have same versions and same issue, tried all suggestions in forums, changing mouse indexes, etc. Trackball is visible in command line but never in RetroArch or MAME.

somebuddy

Again any news on this ? i ran into the same issue. Tested mouse ID 0-10. In console /dev/input/mouse1 is working! but no chance to add it to retroarch to play in scummVM.

[INFO] [udev]: Mouse #0 (/dev/input/event0).
[INFO] [udev]: Mouse #1 (/dev/input/mouse0).
[INFO] [udev]: Mouse #2 (/dev/input/event4).
[INFO] [udev]: Mouse #3 (/dev/input/js2).
[INFO] [udev]: Mouse #4 (/dev/input/mouse1).
[INFO] [udev]: Plugged pad: Microntek              USB Joystick           (121:6) on port #0.
[INFO] [udev]: Pad #0 (/dev/input/event1) supports 0 force feedback effects.
[INFO] [Autoconf]: 1 profiles found.
[INFO] [autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/Microntek              USB Joystick          .cfg
[INFO] [udev]: Plugged pad: Microntek              USB Joystick           (121:6) on port #1.
[INFO] [udev]: Pad #1 (/dev/input/event2) supports 0 force feedback effects.
[INFO] [Autoconf]: 1 profiles found.
[INFO] [autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/Microntek              USB Joystick          .cfg
[INFO] [Joypad]: Found joypad driver: "udev".
[WARN] [udev]: Full-screen pointer won't be available.

digital.arts

@somebuddy
Hi, try this: and read this: libretro docs

Setting up udev permissions

Most Linux distributions prevent users from capturing keyboard/mouse information by default. Only root and users in the group "input" are able to access raw input. This is a security feature in case the system is used by multiple users.

The easiest way to gain access to this input is to:

Step 1: Add your user to the group "input" with the command: sudo usermod -a -G input YOURUSERNAME
Step 2: Log out, and then log back in

If adding your user to the input group does not succeed, you may also set up a udev rule which makes this input accessible to non-root users:

Step 1: Add to /etc/udev/rules.d/99-evdev.rules the following text:
KERNEL=="event*", NAME="input/%k", MODE="666"
Step 2: Reload the rules with
sudo udevadm control --reload-rules.
Step 3: Reboot

mitu

@somebuddy can you post the whole log file on pastebin.com ? Also, please add more info about your system - as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

grant2258

The problem is in retroarch itself there is threads on here how to patch it to work, or just update to 1.7.6. I have no idea why your not updating your system.