[Solved] Trackball not working after 4.3 update

caver01

@majin-wamu Interesting. Well, the Minipac does have TWO interfaces. From the Ultimarc Website:

"Inputs for one 2-axis device (trackball) and one single-axis device (spinner)."

I wonder if lr-mame2003 is picking up the spinner interface and ignoring the trackball in your case.

caver01

@dankcushions @markwkidd Something definitely works differently now in lr-mame2003. I would suggest we regressed. I haven't tested the right-stick core option yet, but something tells me this won't help the way I want/need it to. For those of us who have multiple mouse inputs, how do I make my spinners work for Blasteroids, for example, while my trackball works for Centipede? I might have to revert to using AdvanceMame to get my spinners working again, and @Majin-Wamu will have to stop using 2003 for trackball games.

Any ideas? I think I am coming late to the party, as it had been a while since I updated to the latest versions of the binaries. It could be a months-old change to lr-mame2003 that I am only just seeing now with RetroPie 4.3.

Majin Wamu

@caver01 Thank you caver! This is really helpful. Yeah, in the meantime I will wait it out. The version of Centipede I have doesn't seem to work with other emulators, so I can be patient. I was a little sad at the time, but I trust that the issue will be fixed eventually because the trackball worked before the 4.3 update.

Majin Wamu

@caver01 Hello Caver, please let me know if there are new developments or if you hear back from anyone. Or if there is anything I can do or anyone I can contact.

caver01

@majin-wamu The folks who might know details have been tagged here. Not much else we can do. You could try AdvanceMAME.

markwkidd

@caver01 & @Majin-Wamu is there a way either of you could start an Issue in the mame2003-libretro github tracker? Optimally with a log.

This may be something that the libretro developer casdevel could take a look at unless dankcushions appears with an answer. casdevel is an expert on the libretro input system but they don't seem to read forums much, so I'll be glad to tag them if we can move this discussion to github

Majin Wamu

@markwkidd That sounds like a great idea, but if you can, since I haven't done it before, explain how I can. I do have a github account but never took the time to use it or learn can be done with it.

caver01

@majin-wamu you can install AdvanceMAME using the Retropie configuration menus. It will take some work to configure. Read this, and while you are at it, read the rest of RetroPie documentation.

dankcushions

i'm afraid i have no answer. i may attempt it myself, but doubtful. i've really lost track of all the mouse functionality since all the recent changes.

an error report from someone will progress the issue.

caver01

@dankcushions Do you mean like something from a log? I don't think there are any errors generated, just lost functionality. I'm happy to check somewhere if it helps.

markwkidd

@caver01 said in Trackball not working after 4.3 update:

@dankcushions Do you mean like something from a log? I don't think there are any errors generated, just lost functionality. I'm happy to check somewhere if it helps.

The log will contain details about your mouse devices that is necessary for certain kinds of input debugging.

That said, I have just found out that there is about to be a substantial update to the RetroArch udev input driver. It doesn't have anything specific to do with your error, but it will be worth waiting a day or two to try with the new code.

I'll post here once that happens.

caver01

@markwkidd said in Trackball not working after 4.3 update:

The log will contain details about your mouse devices that is necessary for certain kinds of input debugging.

Where is the log that contains the relevant information? I am happy to grab it.

I am not getting any errors, but if the log is helpful given the fact that I have two mouse devices I will pull it and share.

Majin Wamu

I will wait it out as well, and keeping a close eye open on this board. If the trackball had worked in the past, I don't see why it wouldn't work again in the future. The thing is, what could had possibly caused it to stop working? Like change would effect it?

caver01

@majin-wamu from my perspective, recent changes to mouse inputs has the emulator ignoring all but a single mouse input. In past versions, if you moved ANY attached mouse device, they all would feed input to the emulator. Of course, that meant you could not do two separate mouse devices controlling different things at the same time (like no multiplayer Rampart which has 3 trackballs), but it did allow your trackball to work in games that required it while a set of spinners worked in another game.

Majin Wamu

@caver01 Well I guess their most recent change didn't really fix much sadly. I see what they tried to accomplish, but now I am out of luck. Could this mean there might be a chance it won't get fixed, due to their goal of not having multiple mice control the same thing?

dankcushions

again, the only way anything gets fixed is when people report bugs on github. the multiple mouse thing was absolutely required for proper functionality and the 'all mice are treated as player 1' thing wasn't desirable.

to record logs you need to start the game in verbose mode the runcommand, and then use ssh to access /dev/shm/runcommand.log - paste that here. thanks :)

Majin Wamu

@dankcushions Alright, I will do that. Where exactly should I post the issue on github?

dankcushions

@majin-wamu post it here first so we can take a look. with log files, i'm hoping the issue is obvious.

Majin Wamu

@dankcushions Before I start, you said in verbose mode. I am not sure if I know what that is. I have putty ready to go, are you telling me to run the game in a different way, other than selecting it off of the menu?

dankcushions

@majin-wamu you can launch with verbose logging via the runcommand (the menu that appears before a game is launched).