Multiple mice support in RetroArch cores (lightguns, spinners, trackballs)
-
@space-invader said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
Finally I have no idea on how to put the --verbose option.
you select it via the runcommand - https://retropie.org.uk/docs/Runcommand/
'launch with verbose logging' or something like that. then after exit, the log is in
/dev/shm/runcommand.log
-
@dankcushions
Ok, I will try it too. Thanks! -
@dankcushions said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
you select it via the runcommand - https://retropie.org.uk/docs/Runcommand/
I have added this information to the docs, thanks!
-
Can anyone help me with this? Im trying to play term2 on lr-mame2003 with usb mouse. Retroarch and mame are updated. Raspi sees mouse with cat /dev/input/mice. Verbose logging says event0 for mouse. Set in retroarch accordingly.
Now the trouble:
Im unable to calibrate the lightgun. I cant set mousebutton as button 1 in retroarch input or in mame configuration screen (tab). I cant do anything with the mouse.Ps. Mouse works fine in uae and quake3. Read the docs several times, and tried everything that i can think of.
-
@analoghero said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
Can anyone help me with this? Im trying to play term2 on lr-mame2003 with usb mouse. Retroarch and mame are updated. Raspi sees mouse with cat /dev/input/mice. Verbose logging says event0 for mouse. Set in retroarch accordingly.
Now the trouble:
Im unable to calibrate the lightgun. I cant set mousebutton as button 1 in retroarch input or in mame configuration screen (tab). I cant do anything with the mouse.Ps. Mouse works fine in uae and quake3. Read the docs several times, and tried everything that i can think of.
To confirm, have you built retroarch & lr-mame2003 from source? That is similar to a bug that was solved a week or more ago.
Assuming that is true, could you use
runcommand
to post a log? -
@markwkidd TBH no. Updating from source now. Thought it was fixed.
-
@analoghero said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
@markwkidd TBH no. Updating from source now. Thought it was fixed.
I hope that will do the trick for you, because it does sound like the problem I had with my Wiimote/Dolphinbar before the latest
udev
driver updates. -
Finally I got it working.
I did a fresh SD , watched the mouse indexes with cat order, I have three mouses (mouse1, mouse2 and mouse3) attached, but I didn't realised that my keyboard has a touchpad that acts like another mouse (mouse0).
Started Super Sprint and the touchpad controlled Player1 , Player2 and Player3 at the same time!
With the Retroarch rgui tried to set one different mouse for every player (P1=M1, P2=M2, P3=M3). The touchpad (M0) without action.
But only P2 worked.
I made trial-error proccess and discovered that the mouse indexes that work with retroarch were 0 (the touchpad), 2, 4 and 6 (the three mouses).
Set these last three and it works fine now, although I do not understand very well how :o
I also have the log file, but I do not know how to put it here, if it could be of interest, please tell me how...
Finally thank you all very much for your help and sorry for my bad English... ;)
-
@space-invader You could try pastbin to display your log file to those interested here.
-
@markwkidd It kinda works now. But only one axis is recognised by the game.
Edit: Same in other games. Only horizontal movement of the crosshair. Why is that?
-
@analoghero said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
@markwkidd It kinda works now. But only one axis is recognised by the game.
Edit: Same in other games. Only horizontal movement of the crosshair. Why is that?
Could you check to make sure that you don't have the lr-mame2003 option enabled that is labelled "Share 2 player dial controls across one X/Y device"
That's the last troubleshooting step I can think of. There are people here with more expertise than myself who will hopefully continue to help in this thread :). If after while there's no resolution here you might try posting in the RetroArch forums or by posting an issue in the RetroArch github issue tracker.
In any event, people are going to want to see your RetroArch verbose log (described in the docs) and your retroarch.cfg to help debug. You should copy and paste those two items into a page at pastebin.com or another service, and link to it from forums posts and github issue posts.
-
@markwkidd Yes its disabled. Checked retroarch-core-options.cfg and double checked in the options menu. When i select mouse index 0 now, my logitech wireless keyboards touchpad works as it should.
-
This is my runcommand.log, perhaps it could help somebody.
I'm not sure this is the best way to post it, but I don't know another...
-
So... I finally got the movement fixed. Problem is when my 8bitdo nes30 pro is connected, mouse only works horizontal. Dont know why. Now the next problem is, i cant get the mousebutton to work. Cant assign it in Retroach or in mames config.
FYI On my setup its the same mouse index as @space-invader . Mouse index 0 is keyboards touchpad and mouseindex 2 is usb mouse.
-
@analoghero said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
FYI On my setup its the same mouse index as @space-invader . Mouse index 0 is keyboards touchpad and mouseindex 2 is usb mouse.
This is what I don not understand.
With cat /dev/input/mouse'n' the indexes for my four mouses were 0, 1, 2 and 3. But in Retroarch the working indexes are 0, 2, 4 and 6. -
@space invader Did your mousebuttons work without doing any config? If not what did you do to make them work?
-
@analoghero said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
@space invader Did your mousebuttons work without doing any config? If not what did you do to make them work?
As I have no plans to use them I have not tried, but I will take a look this night and tell you.
-
RetroArch mouse indices are assigned in order they appear in log. As an example, let's look at the relevant part of the log that was posted by @space-invader :
[INFO] [udev] Adding device /dev/input/event3 as type ID_INPUT_MOUSE. [INFO] [udev] Adding device /dev/input/mouse3 as type ID_INPUT_MOUSE. [INFO] [udev] Adding device /dev/input/event0 as type ID_INPUT_MOUSE. [INFO] [udev] Adding device /dev/input/mouse0 as type ID_INPUT_MOUSE. [INFO] [udev] Adding device /dev/input/event1 as type ID_INPUT_MOUSE. [INFO] [udev] Adding device /dev/input/mouse1 as type ID_INPUT_MOUSE. [INFO] [udev] Adding device /dev/input/event2 as type ID_INPUT_MOUSE. [INFO] [udev] Adding device /dev/input/mouse2 as type ID_INPUT_MOUSE.
In this case mice will get following indices:
/dev/input/event3 mouse #0
/dev/input/mouse3 mouse #1
/dev/input/event0 mouse #2
/dev/input/mouse0 mouse #3
/dev/input/event1 mouse #4
/dev/input/mouse1 mouse #5
/dev/input/event2 mouse #6
/dev/input/mouse2 mouse #7If we remove /dev/input/mouse* devices from the list (this is legacy interface, ignore it) we end up with something like this:
/dev/input/event3 mouse #0
/dev/input/event0 mouse #2
/dev/input/event1 mouse #4
/dev/input/event2 mouse #6So, from this log, we can say that this machine has four mouse-like devices and their indices are 0, 2, 4 and 6.
Note that udev driver log format is recently changed to include this indices so that users don't have to figure them out by themselves. For an example, this is how above log should look in the future:
[INFO] [udev] Mouse #0 (/dev/input/event3). [INFO] [udev] Mouse #1 (/dev/input/mouse3). [INFO] [udev] Mouse #2 (/dev/input/event0). [INFO] [udev] Mouse #3 (/dev/input/mouse0). [INFO] [udev] Mouse #4 (/dev/input/event1). [INFO] [udev] Mouse #5 (/dev/input/mouse1). [INFO] [udev] Mouse #6 (/dev/input/event2). [INFO] [udev] Mouse #7 (/dev/input/mouse2).
And remember: /dev/input/mouse* devices shouldn't be used.
-
@analoghero said in Multiple mice support in RetroArch cores (lightguns, spinners, steering wheels):
@space invader Did your mousebuttons work without doing any config? If not what did you do to make them work?
Tried it and mouse buttons don't work.
@casdevel
Understood. Thanks! -
@analoghero I had a similar issue with mouse movement. In my case it was the problem with MAME config files. Try to locate 'default.cfg' file and delete it. I'm not familiar with RetroPie directory structure so I can't tell you where to look for it. If this doesn't help you can also delete game specific config file (it should be in the same directory as 'default.cfg').
Also, this may solve mouse buttons related issues. Just don't forget to bind them in MAME Input settings (e.g. 'RetroMouse1 Left Click' to 'P1 Button 1' and 'RetroMouse2 Left Click' to 'P2 Button 1' for two player setup).
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.