And it makes no sense to me at all.
Again, here’s what I have:
And that’s IT for /dev/input/mouseX. If X > 1, the device node just doesn’t exist.
/dev/input/event3 = Trackball
/dev/input/event6 = Spinner
When I tried cat /dev/input/eventX with event ≠ 3 or 6, I got no input at all from the trackball or spinner.
So when I was in Port 1 Binds, I’d set the Mouse Index to 0, 1, 3, & 6. I’ve seen documentation that says that it’s the event, not the mouse node that matters. But only 0 would work with the trackball. All other numbers would NOT work.
I had, previously, when I had a mouse hooked up (and, I think, when I was using the older version of RetroPie), tried running through 0-10 for Mouse Index in RGUI and got nothing. ONLY 0 would work, and only with the trackball.
But today I tried, almost by accident, using 2 for the Mouse Index and the spinner worked!
I don’t see why. I have mouse0 and mouse1. The only events that showed any input for the mouse devices were 3 & 6, and only when I tested them with
cat /dev/input/eventX, and not with RetroArch at all.
I’m wondering if there could be a bug with the Mouse Index numbers in RetroArch. I would think the Mouse Index would be the same number as the mouse device node or the event node. Or that the index would not skip over a blank. (In this case, it skips 1 - go from 0 for trackball to 2 for spinner.)
So it works. If possible, I’d like to know why, but I’m just glad I got it working. There’s other alterations I want to make to my config, but I didn’t want them to get in the way of this issue, so I’ve waited to do them.
This also provides support for the answer to one of my questions: I used Port 1 for almost everything and Port 2 for the spinner, so that’s proof that the virtual pad for Player 1 can use devices from ports other than 1.