SDL input doesn't detect WMInput-generated event device

[GoogleCodeExporter]

Describe your system:
 - Operating System (be specific): Gentoo Linux (kernel 2.6.37-r4)
 - Machine type (32-bit or 64-bit): 64-bit Phenom Quad-Core
 - Mupen64Plus version: 1.99.4
 - Plugins used: Mupen64Plus OpenGL Video Plugin v1.99.4, Mupen64Plus SDL Audio Plugin v1.99.4, Mupen64Plus SDL Input Plugin v1.99.4, Hacktarux/Azimer High-Level Emulation RSP Plugin v1.99.4

Describe the problem:

I've connected and configured a Wii Remote and classic controller to generate 
input at /dev/input/event2. Mupen64plus v1.5 with blight_input, as available 
from Portage, detects and uses it consistently, but the newer SDL Input plugin 
in v1.99.4 doesn't even seem to notice it's there. Instead I get:

 Input: N64 Controller #1: Using keyboard/mouse
 Input: 1 controller(s) found, 1 plugged in and usable in the emulator
 Input: Mupen64Plus SDL Input Plugin version 1.99.4 initialized.

...even when there is no keyboard plugged in. I've run evtest on 
/dev/input/event2, and it reacts predictably to input from my controller.

Original issue reported on code.google.com by rainesabaal on 8 Jun 2011 at 1:17

[GoogleCodeExporter]

Please send us your blight_input.conf of 1.5 (either in ~/.config/mupen64plus/ 
or ~/.mupen64plus/ ).

You can also use wxmupen64plus and configure the device. Then please send us 
the mupen64plus.cfg from ~/.config/mupen64plus/

Original comment by sven@narfation.org on 8 Jun 2011 at 2:02

[GoogleCodeExporter]

Here's the blight_input.conf that's working.

I wasn't aware of wxMupen64plus, and now it's being outright impossible to 
build after about two hours of trying. Is there a prebuilt 64-bit binary I can 
just download somewhere?

Original comment by rainesabaal on 8 Jun 2011 at 11:02

Attachments:

• blight_input.conf

[GoogleCodeExporter]

I was able to make my controller work by copying the contents of 
blight_input.conf into mupen64plus.cfg. The analog axes are only moving in one 
direction (ie I can move up and left, but not down or right), but I'm confident 
I can fix this with the knowledge and tools I have. If not, I'll open another 
issue.

It seems the problem was that the "device" field under the controller section 
was set to -2, which in-file comments say forces keyboard/mouse. Since I hadn't 
edited this file before, this appears to have been the default setting.

Original comment by rainesabaal on 8 Jun 2011 at 11:46

[GoogleCodeExporter]

It needs wxwidgets2.9 which is nearly nowhere provided - so it is still 
possible to build some kind of static executables, but I would doubt that 
anyone wants to do it. 

Even on gentoo you have to install 
http://packages.gentoo.org/package/x11-libs/wxGTK 2.9.1.1

Ah, and I forgot to ask about the correct string which SDL shows for that 
device. You can get more information about that topic from 
http://www.emutalk.net/threads/49731-Help-us-with-new-Blight-Input-feature?p=427
514&viewfull=1#post427514

Original comment by sven@narfation.org on 9 Jun 2011 at 5:40

[GoogleCodeExporter]

Unfortunately, the user didn't respond. But there seems to be some auto config 
entries for some Wii devices

Original comment by s...@narfation.org on 18 Dec 2013 at 11:40

• Changed state: Fixed