Works a treat! Thank you so much. lr-opera worked on Lemmings with Player 1 as the mouse, it didn't occur to me to try Player 2 for Sega CD.

from the Retropie setup menu in EmulationStation enable Runcommand option select a game to play ... press a button to enter the Runcommand menu and select a lower resolution for the Video Mode than you're currently running the game at. Quote: What is your best source to download the roms? Read Rule No. 2 https://retropie.org.uk/forum/topic/2/forum-rules

Ah, so you're thinking of capturing the mouse up/down movements and sending them to ES as joystick movements. ES wouldn't know the difference. Not bad. My set-up isn't wired to pull this off, but it's definitely an idea. I currently use my trackball as a mouse in PIXEL. It'd be nice to scroll through ES with my trackball, but alas support is not included.

@bobuk1973 You say it works in other applications. Which? How are you running RetroPie/ scummvm - from the desktop or? Which version of scummvm also?

@Bluebotlabs I know what your original post was asking. If you want mouse support right NOW, you can use the pegasus frontend as an alternative. It uses emulationstation's scraped art/gamelist info except for logos/marquees.

That's a good suggestion. I added some notes on persistent device paths.

@mitu Sure! I will post all my findings to help others as well. Thanks for your time.

@mitu said in Are Multiple Mice Supported or Was That Feature Trashed?: You can check by looking at the RetroArch's debug log and by running cat /proc/bus/input/devices. Remembering your first RetroArch debug log, my guess is that RetroArch counts twice a mouse device as both /dev/input/mouseX and /dev/input/eventY. You can check this theory by adding a mouse (so you have 3 devices) and using indexes 0, 2 and 4 to see if each device is detected and working. Okay. I can see that now, with access to the computer again. (Remember, it's in a different place than my desktop, that I use for posting.) Thanks! Now I have the primary Mini PAC set in Keyboard Mode and I see that it recognizes the Mini PACs as devices, but also recognizes the devices on them separately. It looks like keyboard in the Mini PAC gets an event node. Interestingly, the Ultimarc SpinTrak (the spinner) gets Event 5, not 6. When I test with cat /dev/input/event6 I get input from the spinner and I don't with event5. But this shows me that some of the devices are broken down into multiple devices and explains why something else is "in between" the trackball and the spinner. As a side note, even though this is a built in function for RetroArch, I've now done what the manufacturer claims can't be done. Xtensions claims that, in D Input Mode, you can only have one mouse device, so you can have the trackball (somehow that always ends up as the one to take priority) but not the spinner in that mode. I'll be writing them about that! When I have all my questions worked out, I'm going to either write up a few blog pages or make a few videos for others with the same issues. I'm hoping that they will use the so their other customers can get this working, too.

Man, I wish more people were interested in the X68K :(

Got it working under Mame-lr2003, but not sure why. See the ending of this thread for my post about it.

Thank you @mitu That worked, I needed to throw in a --disable-x11 too: CFLAGS="-O2 -march=armv8-a+crc -mtune=cortex-a72 -mfpu=neon-fp-armv8 -mfloat-abi=hard -ftree-vectorize -funsafe-math-optimizations" ./configure --prefix=/opt/retropie/emulators/retroarch --disable-sdl --enable-sdl2 --disable-oss --disable-al --disable-jack --disable-qt --disable-pulse --enable-opengles --disable-videocore --disable-vulkan --disable-wayland --enable-kms --enable-egl --enable-floathard --enable-neon --disable-x11 I may have got rid of the --prefix bit, I can't quite remember now. Appreciate the help. Mr Lightgun

@Cesarpuig said in Mouse like Lightgun in lr-fceumm not work: I don't know how to add the [Solved] tag to the thread Just click on the tree vertical dots at the right of your first post, choose "edit" and put a "[Solved]" before the title manually.

@otello Any suggestions? You can check out the Keyboard Configuration File at /etc/default/keyboard. Not sure if this will help but try this... When you're remoted in, run the RPi Software Configuration Tool with sudo raspi-config and go to Localisation Options then Change Keyboard Layout and run through that to reset those settings.