Mouse Coordinates Not Detected

[blisstik]

Description

According to this page, event indexes should be used for using a mouse.
https://github.com/RetroPie/RetroPie-Setup/wiki/Spinners,-Trackballs,-Lightguns,-and-other-Mouse-Devices

Here is the a log of a game with the mouse attached. As you can see the Mouse #0 is attached to event2. In RetroArch Input settings, I set the User 1 Mouse Index to 0 and I'm able to map the mouse buttons.

The problem is I'm not able to get any coordinate movements from the mouse. There is a warning about Full-screen pointer won't be available. What is causing this issue?

https://pastebin.com/raw/A5e7eDLR

...
[INFO] [udev]: Mouse #0 (/dev/input/event2).
[INFO] [udev]: Mouse #1 (/dev/input/mouse0).
[INFO] [udev]: Plugged pad: MadCatz Madcatz Fightpad (1848:12933) on port #0.
[INFO] [udev]: Pad #0 (/dev/input/event0) supports 0 force feedback effects.
[INFO] [Autoconf]: 3 profiles found.
[INFO] [autoconf]: selected configuration: /home/pigaming/.config/retroarch/autoconfig/MadCatz Madcatz Fightpad.cfg
[INFO] [Joypad]: Found joypad driver: "udev".
[WARN] [udev]: Full-screen pointer won't be available.
...

Expected behavior

Mouse coordinates to move.

Actual behavior

Mouse coordinates are not moving but mouse buttons can be mapped without issue. I've ran a test using advmame and the coordinates move for the advmame test.

https://pastebin.com/raw/JRbHiH0T

Steps to reproduce the bug

On an Odroid XU4, using the ORA v1.5.2 image

1. Update RetroPie-Setup script
2. Update RetroArch
3. Update lr-reicast
4. Attach a mouse
5. Launch a game like Sports Shooting USA

Version/Commit

• retroarch - bd64deb
• lr-reicast - a45420f

Environment information

• OS: Ubuntu 16.04.3 LTS (GNU/Linux 3.10.105-141 armv7l)

[singularity098]

Hi. I came here to log what I believe is this same issue, but glad to see someone else had written it up, and just recently. I wanted to share some more information and ask if you could confirm that information on your system to see if we can help narrow this down.

What I noticed is that I cannot map the mouse movement at all, as you have said. I started to wonder if this was core-specific or platform specific. Here is what I found in testing:

MAME (git core, v0.203): Fail
MAME 2016: Fail
MAME 2014: Fail
MAME 2010: Pass! I can use the mouse/trackball in games like Centipede.
Final Burn Alpha: Fail
SNES9x: Pass! I was able to play Mario Paint after selecting mouse in the core specific input options.

Interesting... Additionally, I tested some other environments. This was my result:

RetroArch 1.7.5 in Ubuntu 18.10: Failures as described above
RetroArch 1.7.3 in Lakka 2.1.1: Failures as described above
RetroArch 1.7.5 in Windows 10: Pass! I did not experience any of the core-specific issues described above, the mouse works in all of the cores.

Is any of this consistent with what you're seeing? Thank you, sir. I hope this issue can get resolved!

[blisstik]

The only other game I tried was Terminator 2 using lr-mame2003-plus. Oddly enough, the pointer only worked vertically.

[blisstik]

I've tried a SteelSeries wired mouse and a logitech 2.4ghz mouse.

[blisstik]

This did not fix the issue. Mouse buttons work but still will not move.

[singularity098]

If you load a game in MAME, and then pull up the quick menu, then proceed to the core specific "Options", do you see an option for "Enable in-game mouse" which is turned to off?

Turns out this was the source of the issue for me. This option was turned off by default in the git (most recent) MAME core for Linux, but not for MAME 2010.... odd.

I wonder why that would be set to "off" by default, and I wonder if the default value there could be changed.

[blisstik]

I tried fceumm with Duck Hunt and I was able to get it to work. I didn't have to compile RetroArch with the PR.

[blisstik]

Can you elaborate on mouse abs? Just a quick explanation why certain mouse won't work? Since lr-fceumm work and lr-reicast doesn't, probably means the lightgun api isn't properly coded. It's looking like it's not a retroarch issue.

…

________________________________ From: grant2258 <notifications@github.com> Sent: Saturday, December 15, 2018 9:43 AM To: libretro/RetroArch Cc: 6alileo; Author Subject: Re: [libretro/RetroArch] Mouse Coordinates Not Detected (#7697) yea well that means you mouse supports abs people that dont have this support will need that patch. It must just be the core option in your case hopefully. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7697 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AoSfFITlxtwGVVXc_GdkNh7ou5tRZ6kSks5u5TS4gaJpZM4ZBBsa>.

[blisstik]

I'm using udev and trying to get lr-reicast - Ninja Assault to work. I'm able to map the mouse buttons but coordinates will not work. In the same environment and RA version, lr-fceumm works after turning on the zapper as mouse core option. Lr-reicast doesn't have this feature.

…

________________________________ From: grant2258 <notifications@github.com> Sent: Saturday, December 15, 2018 10:28 AM To: libretro/RetroArch Cc: 6alileo; Author Subject: Re: [libretro/RetroArch] Mouse Coordinates Not Detected (#7697) Ok well first and foremost this only applies ( in my scenario here) if your are using the udev driver. A mouse can report its coordinates as relative or absolute or both. The old code had a bug where when it didnt support abs it would close the mouse device down. go to you settings driver->input driver what is this set too in linux for you? Im a bit lost here in what you are trying to do what do and what emulator your having trouble with in particular. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7697 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AoSfFD2xr4cnNQdUjXjBzsQrIHKgYAB2ks5u5T9DgaJpZM4ZBBsa>.

[blisstik]

Yes. I've tried mouse and lightgun. This setting applies concurrently with the input 1 setting as well.

…

________________________________ From: grant2258 <notifications@github.com> Sent: Saturday, December 15, 2018 10:46 AM To: libretro/RetroArch Cc: 6alileo; Author Subject: Re: [libretro/RetroArch] Mouse Coordinates Not Detected (#7697) https://github.com/libretro/reicast-emulator/blob/37da602d6421b755ae045171d17c8d4328c7dcc0/core/libretro/libretro.cpp#L438-L445 have you looked in quick menu->controls-> user 1 device type and changing that to mouse ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7697 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AoSfFExhcQ635k2cAGia84r3oGaSUyNvks5u5UObgaJpZM4ZBBsa>.

[blisstik]

What I meant was changing input 1 to mouse also changes it in quick menu controls.

…

________________________________ From: grant2258 <notifications@github.com> Sent: Saturday, December 15, 2018 10:46 AM To: libretro/RetroArch Cc: 6alileo; Author Subject: Re: [libretro/RetroArch] Mouse Coordinates Not Detected (#7697) https://github.com/libretro/reicast-emulator/blob/37da602d6421b755ae045171d17c8d4328c7dcc0/core/libretro/libretro.cpp#L438-L445 have you looked in quick menu->controls-> user 1 device type and changing that to mouse ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#7697 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AoSfFExhcQ635k2cAGia84r3oGaSUyNvks5u5UObgaJpZM4ZBBsa>.

[barbudreadmon]

On odroid, fbalpha is working as expected with games using analogs when setting mouse as control, i'll try to hook the pointer/lightgun libretro device (they are basically the same) this week-end to see if i'm experiencing issues on my odroid with it.

[barbudreadmon]

The pointer is also working as expected in fbalpha, so the issue might be with the cores indeed, a wild guess would be some type conversion going bad on arm, 2 related issues i had to deal with in the past :

• char, which is unsigned by default (unlike x86)
• implicit conversion of negative float to unsigned int

[barbudreadmon]

Ok, i figured out the issue, i'll go into details, there are 3 ways to deal with mouse/pointer/lightgun devices in RA :

• using RETRO_DEVICE_MOUSE, it's detecting mouse relative movements, basically it works like an analog stick
• using RETRO_DEVICE_POINTER, it's detecting mouse/touch absolute position, so you can set the cursor in the game directly to coordinates
• using RETRO_DEVICE_LIGHTGUN, it's detecting lightgun absolute position, so you can set the cursor in the game directly to coordinates

The deal here is that we are using RETRO_DEVICE_LIGHTGUN in lr-reicast (and probably in a lot of other cores), because mouse is actually able to emulate a lightgun on a desktop computer (might be something related to the usage of a window manager system, or some specific code in RA, idk), but on odroid (and probably some other platforms) the mouse doesn't seem to emulate the lightgun, so we'll have to implement a RETRO_DEVICE_POINTER device as a workaround to get this stuff to work.

Edit : It seems to be related to the usage of a window manager system indeed, maybe it would work on wayland with the current code ? A proper way to fix this would be to backport 7dfcc16#diff-70ed405993338684f64b3107991cbc8e to the RA udev driver.