Emulator

This is assuming you have a DualShock 3. If you have one and you'd like to
get it working, look around on this site: www.motioninjoy.com

What steps will reproduce the problem?

1. Plug in your controller (in this case, i'll be plugging in my ds3)
2. Make sure your controller's working and can be found in Windows
3. Open up Dolphin
4. Go to Options>Configure
5. Click on the Plugins tab
6. From the drop down box of the Pad plugin, select nJoy 0.3 and click on
   "Config..." right next to it
7. Configure your controller, but most importantly, enable rumble
8. Close the configuration window and run a game. The following should show
   up (or something similar):

Device 1 doesn't seem to work !
Rumble for device 61952 is now Disabled !

Device 2 doesn't seem to work !
Rumble for device 61952 is now Disabled !

Device 3 doesn't seem to work !
Rumble for device 61952 is now Disabled !

Device 4 doesn't seem to work !
Rumble for device 61952 is now Disabled !

Then the game will resume like normal, and will actually be playable with
your controller. However, just as the error message says, rumble has been
disabled and will not work.

What is the expected output? What do you see instead?
I expect rumble support, since lilypad/pj64/epsxe and some other misc games
that support rumble can use it. However, nJoy yells at me because somehow
the device doesn't work - but it clearly does.

What version of the product are you using? On what operating system?
Dolphin R3971 x64 - Windows 7 x64 7600

Please provide any additional information below.
This is both a request and possibly a bug report. Bug report because I'm
sure nJoy would've been able to see the rumble - but you can't specifically
configure the motor(s) (saw/constant/etc) separately. Request because it
would be nice to have some more specific settings for rumble (as well as
other things) - like lilypad.

However, DS3 support for the PC is sorta a hack job, but the thing is - if
rumble works for other emulators and games, it should work for Dolphin as
well. So maybe it's just the way nJoy identifies either a controller has
motors or not? Not sure, but I hope you figure it out.

Thank you (this should be the last issue report I make - providing I come
across something in linux again)!