[SOLVED] Undetected Wiimote Input - Resident Evil Darkside blah

[AuraDragon]

Okay, I didn't want to have to post this, since as most technical things come I am able to solve them myself, eventually...

Anyway getting straight to the point: Since the first game I was trying to run was Resident Evil's rail shooters, I had to use a Wiimote, and I don't have any I decided to use my USB Logitech RumblePad 2 controller and keyboard/mouse.

When I use the original Wiimote plugin (the one that comes with 'official release') I can't use my controller to play the game, I can set the controls in the options menu, but when I get in game no controller button works.

Additionally I tried the Incomplete Wiimote Plugin (the one that comes with the latest SVN build on dolphin-emulator) but that one didn't even recognize my mouse input ingame.

I'll post a picture of my wiimote plugin settings if required, until then I'm gonna keep trying different settings and revisions.

tl;dr Neither wiimote plugin works.

SPECS:

Windows 7 x64 Ultimate
Intel i7 860 2.8ghz
AMD Radeon HD 5850
8gb Memory
USB Logitech RumblePad 2 (plugged in to a USB2 slot, can be plugged in to a USB3 slot if required)
Generic Microsoft Keyboard and Mouse

Dolphin Official 2.0 and
Dolphin r6214

[Billiard26]

Show your config for the new wiimote plugin.
Screenshot or ini file, whichever you prefer.

[AuraDragon]

http://i116.photobucket.com/albums/o15/A...Plugin.png
http://i116.photobucket.com/albums/o15/A...arbage.png

Player 2's input source is set to None since not even Player 1 works yet.

I've already tried Background Input, and turning on the Nunchuk but I never assigned it buttons.

I have also readied pictures of the original wiimote plugin settings.

[Billiard26]

Your config looks fine.

Some games are having issues with wiimotes after revision 6177.
Try a build of revision 6176 or older and see if the problems persist.

[AuraDragon]

It works with the 6176 revision, now all I have to do is fix the sensitivity on the controller.

Thanks for all the help Billiard, that was a simpler solution than I expected.

[Billiard26]

You could try r6216, it fixed an issue caused by r6214 that I wasn't aware of before.
I'm not sure if the issue you are having is caused by 6177 or 6214.

[AuraDragon]

Okay, well I tried both versions 6216 and 6177, they both seem to work, it seems like 6214 was the problem. Thanks again for the help.

If you want me to try 6212 and 6214 to see if it really is the problem just say so and I'll try.