Oh actually I did a mistake...
For some reasons, I thought all mames were the same emulators and used a shared folders for roms (like genesis).
So mame4all wasn't showing up since there was no rom in...

I put the shooting games in the mame4all folder, now I have 2 mame menus on retropie.

The mouse is working with this games on Mame4all.

@ExarKunIv I know this was some time ago, but I am trying to make my joystick act like a mouse in DOSbox. Do you remember where that file you made is stored?

@jonnykesh No problem. It's just on a Rapsberry Pi 3b with Retropie 4.3. Had the same issue on 4.2.

That's a shame. I was hoping it was something I could fix on my own. I do love my Japanese computers. I'm glad to see that an official Retropie guide for the PC-88 emulator showed up within the past few months at least.

As of this week, RetroArch supports multiple mice in all cores that have their own support for one or more mice. As long as the original emulator that the libretro core is based on has mouse support, the libretro version should as well.

If a core which should have mouse support doesn't work when thus configured, there is at least one libretro dev who is actively looking for cores to fix for mouse support, so new github issues are welcome.

In other words: what are you trying to do that isn't working?

@backstander

I think I'll need to level up a few more times.

It's really more intimidating than it is difficult. After you've written a couple of commands and learn a few troubleshooting measures, it becomes as routine as anything else.

i know is a older post, but here is my map for Worms Reinforcements (1996) for "Dragonrise inc, generic usb joystick", similar PS2 gamepad, using joymap-0.4.2 the dpad controls aim and movement, leftstick analog controls the mouse, L1 & Start buttons for Left - right mouse buttons, square is "enter", cross is "spacebar" and R2 for" control "& right trigger for "f9" ( a combination that quits emulator)

**# Mapping for worms for dragonrise

# Map mouse
axis vendor=0x0079 product=0x0006 src=0 target=mouse axis=0 min="0" max="255" speed="16" deadzone="127"
axis vendor=0x0079 product=0x0006 src=1 target=mouse axis=1 min="0" max="255" speed="16" deadzone="127"

button vendor=0x0079 product=0x0006 src=4 target=mouse button=0
button vendor=0x0079 product=0x0006 src=9 target=mouse button=1

# Actions
axis vendor=0x0079 product=0x0006 src=17 target=kbd plus="down" minus="up" flags="trinary"
axis vendor=0x0079 product=0x0006 src=16 target=kbd plus="right" minus="left" flags="trinary"

button vendor=0x0079 product=0x0006 src=2 target=kbd button="space"
button vendor=0x0079 product=0x0006 src=8 target=kbd button="esc"
button vendor=0x0079 product=0x0006 src=3 target=kbd button="enter"
button vendor=0x0079 product=0x0006 src=7 target=kbd button="leftctrl"
button vendor=0x0079 product=0x0006 src=11 target=kbd button="f9"**

@skepticalgeel no clue. On the Pi, it all runs full screen and not from a desktop.

@mediamogul yeah I just did, and still the same. I even tried copying the love files over from another install and still the same. I will have to test love on that Pi later to see if it's the same, but last time I tried it wasn't.

The default virtual keyboard (matchbox-keyboard) has an issue where the desktop becomes unresponsive while the keyboard is open, so use xvkbd instead. I'll edit this post with instructions later

ok i finally uploaded everything and made a readme on github. Everything works now, when mouse mode is active the keys from your buttons are not registered anymore and you can switch between mouse mode and your normal input method. you specify and remap existing keys of your encoder specifically for use in mouse mode (you tell it if i press this button which is key CTRL for example then send key F5 instead). You can specify 6 keys like this.

i did not find a game yet that did not work with this version, my readme needs work though but it's a rather long readme for something simple to setup

@i8allUrPi

I really appreciate your time and effort.

Not a problem. I'm glad it all worked out.

@LiqwdE I think I know what you mean. The type of connector that used to come on the old PCMCIA laptop cards back in the day.

My little pi zero is flanked by a microcontroller and a lithium battery protection board, you can read the whole project here

https://retropie.org.uk/forum/topic/2089/yet-another-pi-zero-portable

I normally make my photos backup to my Google drive then just right click and copy the image URL from photos.google.com seems to work ok

@RetroNoob can you see that message on top of every single page of this forum?
I'm pasting here for you:
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@PiE81
Kind of unrelated and I did this a long time ago but here's how I got lr-quake working with a keyboard:
https://retropie.org.uk/forum/topic/1884/full-keyboard-support-for-libretro-tyrquake-quake/2

@barbudreadmon Thanks, that sounds great. I'll test it today or in the next days. My Pi is doing the update from source right now, but I don't know yet if I'll have the time to test it later today.

AFAIK there should be no need of different mouse devices for trackball/spinner/lightgun, because they all use the same /dev/input/event… devices. (Multiple mouse devices may be needed for games with multiple mouse-type devices, though.)

Trackballs and lightguns will use both axes of a mouse device, whereas spinners will use only one axis per spinner. For two spinners, that may be X and Y of a single mouse device if they are connected that way. Others, like the USB adapters that come with the SpinTrak spinners, will map them as separate mouse devices and only use their X axes.

https://retropie.org.uk/docs/Spinners,-Trackballs,-Lightguns,-and-other-Mouse-Devices/ describes the different kinds of axis mappings in great detail.