Wii remote for use a gun
-
@mediamogul said in Wii remote for use a gun:
I've just run a few tests and got some disappointing results. The first test was with two standard mice on lr-mame2003 running 'Terminator 2'. I'm on the latest nightly, I have the input driver set to 'udev' and the player 1 & 2 mouse index set to 0 and 1 respectively. Unfortunately the player two mouse was completely unresponsive. There may be a piece to the puzzle I'm missing, but at first blush it looks like the mouse index feature isn't working on the Pi.
The second test was with the DophinBar and WiiMote. Here I tested with lr-mame2003, lr-nestopia, lr-Genesis-Plus-GX and lr-snes9x2010. All the cores registered the mouse clicks, but would not register any movement. Finally, I tested an Ultimarc USB arcade gun and received the same results as I did with the DolphinBar. As I went along, I tested to make sure the system was reading the various mice with
evtestand they all checked out.it might be worth trying with the linuxraw driver.
just to confirm from the other thread - you are using the latest nightly, yeah? i.e., currently the only way to get that is to edit the retroarch.sh script before the source compilation, otherwise it will get v1.6 or something like that.
-
it might be worth trying with the linuxraw driver.
I'll try that this evening.
just to confirm from the other thread - you are using the latest nightly, yeah?
I modified the script module from
gitPullOrClone "$md_build" https://github.com/libretro/RetroArch.git v1.6.0to
gitPullOrClone "$md_build" https://github.com/libretro/RetroArch.gitand it seemed to build the latest without any errors. All the most recent additions are intact, such as mice indexes and menu transparency for XMB, but maybe there are additional considerations to allow the multiple mice to function.
-
@mediamogul it might be worth asking on the github issue: https://github.com/libretro/RetroArch/issues/4775
also did you rebuild mame2003 from source? again it needs the latest version.
i've been meaning to test this myself, just not got around to it :(
-
@dankcushions said in Wii remote for use a gun:
@mediamogul it might be worth asking on the github issue: https://github.com/libretro/RetroArch/issues/4775
I second posting on hithub assuming you've got latest mame2003 core.
-
it might be worth asking on the github issue: https://github.com/libretro/RetroArch/issues/4775
I second posting on hithub assuming you've got latest mame2003 core.
Certainly. After I exhaust any suggestions here, I'll be sure to post.
also did you rebuild mame2003 from source? again it needs the latest version.
I took for granted that it might not be necessary. I'll try that this evening as well. I take it that the same goes for all the other cores I'm testing with.
i've been meaning to test this myself, just not got around to it :(
Meanwhile Terminators are taking over the Earth, the duck population is wildly out of control and Aerosmith are prisoners of a senseless war. Where are your priorities man?
-
I took for granted that it might not be necessary. I'll try that this evening as well. I take it that the same goes for all the other cores I'm testing with.
i can't speak for the other cores, but certainly the latest RA and mame2003 SHOULD enable multiple mice to be used. previously it worked ok with one. i'm not sure about pointer vs absolute devices and changes around those in other corees - that's a bit of creep from what this github issue is about, but maybe that code has changed also.
-
Tonight, I focused on lr-mame2003 running 'Terminator 2'. I compiled the latest 2003 nightly and tested both udev and linuxraw as the input drivers. All combinations came with the same results as last night. The two standard mice will not function at the same time, despite the 'mouse index' setting. Each mouse would operate on it's own, so long as it occupied the mouse0 assignment from the system.
The same holds true with the dolphinBar, except it never registers movement, only clicks when it's occupying the mouse0 assignment from the system. I'll post to the github thread linked above sometime tomorrow, but I'll make sure to only mention the mouse index situation, as it looks like absolute coordinates will be a separate issue.
-
@mediamogul can you please post your
/opt/home/pi/RetroPie/configs/all/retroarch-core-options.cfg? specifically i'm checking to see that the mame2003-mouse_device setting is set to 'mouse' rather than pointer.FYI it looks like they've closed the issue here: https://github.com/libretro/RetroArch/issues/4775
but i'm not sure anyone tested it using pi + udev + raspbian, etc. you may have found a bug!
-
Ah nice, I forgot about that setting.
mame2003-mouse_device = "mouse"Would that affect the multiple mouse feature, or just the absolute coordinates?
-
@mediamogul said in Wii remote for use a gun:
Ah nice, I forgot about that setting.
mame2003-mouse_device = "mouse"Would that affect the multiple mouse feature, or just the absolute coordinates?
it just makes sure that it listens for a mouse device (ie, standard USB mouse), and following these changes, multiple mice, in theory! it definitely works with one mouse.
BTW you need to make sure you're using a game that understands a mouse device. my test case was always centipede. i didn't test terminator 2 - best to stick with centipede IMO.
if you change the mouse_device to "pointer" mame2003 should understand any recognised absolute devices, but i believe previously the UDEV driver had difficulty with them. absolute devices aren't really covered in these changes AFAIK. best to leave those for the moment.
-
best to stick with centipede IMO.
Shouldn't I be testing with a game that would support two mice, or do you just mean for testing pointer devices?
-
Above, it was thought that better support for pointer devices would come as a side-effect from the recent addition of multiple mouse support for RetroArch. This would have directly related to this thread, but since it isn't the case, it's probably best to continue this discussion here where it's not so off topic.
-
@BGallagherLA Hi there yes it's paired to the dolphin bar. Plugged into the usb of the pi3.
Sorry it's taken a long time to respond I have been off line so to speak -
This post is deleted! -
@masterful No, you have to go into Retropie settings and pair the Wiimote to your Pi's built-in Bluetooth, after plugging in the DolphinBar. If you did that, then I don't know... I have never had to calibrate anything in AdvMame 1.4 and it's very accurate (except for maybe one or two games, out of like 50).
-
Also, in case anyone is interested, I put a video together a week or so ago, showing how my setup works on Lethal Enforcers and Operation Wolf -
-
@BGallagherLA
Ok that might help. I've been trying to install touchmote software and I don't think that's been helping me.
I will pair it with the pi3 Bluetooth then try again.
Just compiling a list of 5 games to try.
Thanks for all the help -
@masterful Ah, yeah I don't know what that software is, but as long as you have these games in AdvMame 1.4, you dont have to calibrate anything, except mapping extra buttons on a few games like Operation Wolf, otherwise, trigger works automatically and crosshairs move right away. I have like 50 games that work in this setup, and you can see two that work in the video above, Lethal Enforcers and Operation Wolf. I can get you a full list of the games that work on my setup if you want.
-
-
@BGallagherLA i too would love a full list. Any chance you could post your config/s for these games. I plan to use advmame only for these games with the dolphinbar so it would save me a lot of time.
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.