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

(Solved) Unable to get Trackball working with Mame2003.



  • Hi All,

    First the relevant details.

    Pi Model or other hardware: PI3
    Power Supply used: Standard 2A USB charger
    RetroPie Version Used: 4.4.4
    Built From: Manually installed on top of
    USB Devices connected:
    Controller used: USB Joystick controller with buttons etc (working), PS2 Trackball (Not working in Mame)
    Error messages received: None
    Log found in /dev/shm/runcommand.log (if relevant):
    Guide used: n/a
    File: n/a
    Emulator: mame2003
    Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)

    runcommand-centipede.log
    runcommand-missile.log
    retroarch-core-options.cfg

    How to replicate the problem: Start up a Trackball game (Missile Command or Centipede) and the Trackball does not work

    I have tried to follow the Wiki and setup a PS2 Trackball on my PI, but cannot get it working under Mame2003.

    I have tested this under the Linux OS and the input devices are responding and accessible from the userid Emulationstation/Mame is running as.

    mouse0 (Track Pad)
    mouse1 (KB Mouse)
    event0 (Unknown)
    event1 (Track Pad)
    event2 (Unknown - Constant Input)
    event3 (KB Mouse)
    js0 (USB Joypad Controller)
    mice (Track Pad & KB Mouse)

    In the Verbose logs I see the following:
    [INFO] [udev]: Keyboard #0 (/dev/input/event3).
    [INFO] [udev]: Keyboard #1 (/dev/input/mouse1).
    [INFO] [udev]: Keyboard #2 (/dev/input/event0).
    [ERROR] [udev] Failed to open device: /dev/input/event3 (Success).
    [INFO] [udev]: Mouse #0 (/dev/input/mouse1).
    [ERROR] [udev] Failed to open device: /dev/input/event1 (Success).
    [INFO] [udev]: Mouse #1 (/dev/input/mouse0).
    [INFO] [udev]: Plugged pad: DragonRise Inc. Generic USB Joystick (121:6) on port #0.
    [INFO] [udev]: Pad #0 (/dev/input/event2) supports 0 force feedback effects.

    Does this mean that both the Trackball and the Keyboard/Mouse combo is being refused access?

    In my retroarch-core-options.cfg file I have added the following lines:

    input_player1_mouse_index = "0"
    mame2003-mouse_device = "mouse"
    mame2003-trackball_device = "mouse"
    mame_current_mouse_enable = "enabled"
    mame2003-dial_device = "mouse"

    I have attached the Config files and the verbose logs here. I did see another thread that said Mame2003 was broken for Mouse/Trackball devices, is that the case?

    I attempted to run AdvMame, but the Roms I have I assume are not compatible, as I attempted to start it, but it just dropped my back to the menu.

    Any advice would be great,

    Many Thanks,

    Paul


  • Global Moderator

    @MrRalphMan I think there was a bug in the mouse support in certain configuration in RetroArch, which was fixed recently by @grant2258 in RetroArch - see this topic which you might have stumbled upon.
    Since the fix is not yet in the RetroArch package from RetroPie, you could try to compile from source using the instructions from here, kindly provided by @hhromic.





  • @MrRalphMan said in Unable to get Trackball working with Mame2003.:

    Standard 2A USB charger

    You also need a power supply rated at 2.5A+ and NOT a charger.



  • @rbaker said in Unable to get Trackball working with Mame2003.:

    @MrRalphMan said in Unable to get Trackball working with Mame2003.:

    Standard 2A USB charger

    You also need a power supply rated at 2.5A+ and NOT a charger.

    Hi, Thanks I have now tried it with a proper supply, I've not had an issue with using this Charger perviously and do not get the 'Undervolt' messages with it.

    @mitu said in Unable to get Trackball working with Mame2003.:

    @MrRalphMan I think there was a bug in the mouse support in certain configuration in RetroArch, which was fixed recently by @grant2258 in RetroArch - see this topic which you might have stumbled upon.
    Since the fix is not yet in the RetroArch package from RetroPie, you could try to compile from source using the instructions from here, kindly provided by @hhromic.

    Thank you, I have following this and I am almost there. Currently I have a wireless Keyboard/Mouse and the Trackball connected to the PI. With the newly compiled retroarch I can now use the KB's Mouse, but not the track pad.

    I've removed as much of the manual config I added to the /opt/retropie/configs/(all|mame-*)/retroarch-core-options.cfg config files and have changed the Mouse index by actually running retroarch and setting the Player1 Bindings. I've tried 0 thru 3 and each time the KB Mouse works, but the otherone doesn't.

    Looking at the Event inputs I see the following:

    event3 - KB Mouse
    event1 - Trackball

    And in a verbose log I see the following:

    [INFO] [udev]: Keyboard #0 (/dev/input/event3).
    [INFO] [udev]: Keyboard #1 (/dev/input/mouse1).
    [INFO] [udev]: Keyboard #2 (/dev/input/event0).
    [INFO] [udev]: Mouse #0 (/dev/input/event3).
    [INFO] [udev]: Mouse #1 (/dev/input/mouse1).
    [INFO] [udev]: Mouse #2 (/dev/input/event1).
    [INFO] [udev]: Mouse #3 (/dev/input/mouse0).

    So my Mouse Index should be #2?

    Many Thanks all for the help.

    Paul


  • Global Moderator

    @MrRalphMan I see 3 mouse devices created and /dev/input/mouse1 is the one on the Keyboard. Simplest way to determine which mouse is the trackball is to use evtest with each device and move your trackball to see if you get any input from it.



  • @mitu said in Unable to get Trackball working with Mame2003.:

    @MrRalphMan I see 3 mouse devices created and /dev/input/mouse1 is the one on the Keyboard. Simplest way to determine which mouse is the trackball is to use evtest with each device and move your trackball to see if you get any input from it.

    Thanks for the reply, I cat'd the individual input objects to determine that events that related to the devices.
    Not sure where the third mouse has come from. 😁



  • @MrRalphMan said in Unable to get Trackball working with Mame2003.:

    [INFO] [udev]: Mouse #0 (/dev/input/event3).
    [INFO] [udev]: Mouse #1 (/dev/input/mouse1).

    [INFO] [udev]: Mouse #2 (/dev/input/event1).
    [INFO] [udev]: Mouse #3 (/dev/input/mouse0).

    the events are abs functions for that mouse is its supported



  • Ok, this is now resolved.

    I did nothing mote then not boot with the Wireless KB Controller plugged in and it is now working, thanks for all the help.

    Many Thanks,

    Paul

    *** Can I mark this as solved or something? ***


  • Global Moderator

    @MrRalphMan said in Unable to get Trackball working with Mame2003.:

    *** Can I mark this as solved or something? ***

    Modify the topic subject and add a Solved at the beginning.



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.