MAME 2003 and the trackball issue - Retropie 4.3.12
-
Re: [Solved] Trackball not working after 4.3 update
After looking through the above thread I have exhausted all my efforts. There is some great info in there but I have tried it all. I have a xin mo arcade controller plugged into port 1 (has 2 players that show up port 1 and 2 in retroarch) Then a USB trackball plugged into port 2. Mouse works as I used the following command - cat /dev/input/mouse0.... trackball showing input. Tried adding the lines in retroarch.cfg and retroarch-coreoptions.cfg -
(mame_current_mouse_enable = "enabled" and input_player1_mouse_index = "0")
I also tried switching mouse indexes within retroarch user binds. Even tried adding the input_player1_mouse_index = "0" into game specific cfgs. Still cannot get the trackball working. And it use to work fine way before 4.3 as I haven't made a trackball build in some time now. Here the relevant part of the log file... I hope someone can help me with this.[INFO] [udev]: Keyboard #0 (/dev/input/event0).
[ERROR] [udev] Failed to open device: /dev/input/event1 (Invalid argument).
[INFO] [udev]: Mouse #0 (/dev/input/mouse0).
[INFO] [udev]: Plugged pad: Xin-Mo Xin-Mo Dual Arcade (5824:1505) on port #0.
[INFO] [udev]: Pad #0 (/dev/input/event2) supports 0 force feedback effects.
[INFO] [Autoconf]: 1 profiles found.
[INFO] [Autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/Xin-Mo Xin-Mo Dual Arcade.cfg
[INFO] [udev]: Plugged pad: Xin-Mo Xin-Mo Dual Arcade (5824:1505) on port #1.
[INFO] [udev]: Pad #1 (/dev/input/event3) supports 0 force feedback effects.
[INFO] [Autoconf]: 1 profiles found.
[INFO] [Autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/Xin-Mo Xin-Mo Dual Arcade.cfg
[INFO] [Joypad]: Found joypad driver: "udev".
[WARN] [udev]: Full-screen pointer won't be available. -
Would you be able to add a small description of what you did to solve your problem? I have a trackball on the way so it may prove useful if I have any problems. Thanks
-
Looks like this topic has been covered pretty thoroughly so we most likely wont get any response. A shared .cfg file would have helped but whatever... must be very classified info! Anyhow if it doesn't work for you just do what I did and grab the mame-advance versions of the roms (.106). I tested about 70 of them... work just fine. Just refer to the linked thread. Just a simple line edit in the mame RC file. You will lose the retroarch bezel support but can use the old style mame bezels. I chose not to as they shrink up too much of the screen. Good luck!
-
@chuckyp While @drewjbx shared a link and says the problems were solved by using AdvanceMAME, we never really got enough details to help with troubleshooting. Saying "tried it all" is in fact not really saying anything that we can use to help. The fact is that many of us with complicated setups are using analog devices successfully in lr-mame2003. For example, I think my box identifies at least three different mouse devices. I have an Ultimarc UTRAK and two (2) Turbo Twist spinners. Mine may not be the most complex Pi arcade system out there, but I am happily using it in lr-mame2003 where I want to.
The changes in RetroArch referenced in the link above did require some of us to add core configs in order to make things work the way we want, but it also enabled the ability to matrix inputs, something that was not possible before. For instance, I can get my trackball working in Golden Tee while blocking the spinners--this was not possible before. This is a win because the spinner lets you make perfectly straight shots--cheating, really.
I think with shared logs and config files, we might have been able to help @drewjbx. That said, AdvanceMAME does have clearer and and superior configurations possible, so going that route is not a bad play either.
When your trackball arrives, take a look at the wiki first.
-
Will do. Thanks
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.