No controller vibration after cleaning Xbox 360 controller, but...

CPUzX

Reputable
Jun 12, 2015
83
0
4,640
Hello

When I first got my gaming PC running, I configured my Xbox 360 wireless controller with Windows 7 (64x) and in the process I realized I had to use third-party drivers for the unofficial wireless receiver, but everything worked perfectly during that time; however when I started noticing a very annoying squeak coming from the right analog, I decided to take the controller apart in order to put WD40 on the analog, and I put quite a lot on there because I couldn't determine the exact spot to put any directly, but I made sure to leave it overnight and dry it with a cloth too, so in the morning I put half of it back together and tested it, and it still worked, so I put everything back together fully, but after doing this, the vibration rumble stopped working, but I don't understand, because rumble works in Dolphin emulator, and it also works in the controller configuration rumble tests within Dolphin, but when I play Steam games such as Killing Floor 2 and Dragon Ball Xenoverse, it doesn't work at all, even with the rumble function selected on those games. When I tested Sonic Generations, the rumble worked, but I can't remember if the rumble is right, or if it might be too faint now. I'm thinking maybe I damaged the rumble IC on the controller perhaps, but it appears to work in Dolphin, not Steam. I know the rumble feature isn't very important, but going from console to PC, the controller is all I use for now. I've got to get used to the mouse/keyboard, ideally, as I've heard it's very very accurate for FPS shooters anyway, but please can someone direct me to the possible cause/fix?

The batteries are brand new Duracell.
I can't test everything works with an Xbox 360, as I don't have one, or an extra 360 controller.
Thanks!
 
First of all, WD-40 is not a lubricant.

There is one of 2 things wrong with it.

1. You broke one of the thin wires to one of the vibration motors. You will need to solder it back on if this is the case.

2. The motor is being stopped by an obstruction in the controller or it was put back together incorrectly.

Number 2 is the most likely IMO. If the motor is slightly misaligned it will get stuck and not vibrate. You need to take it back apart and see which one it is. If the rumble is more faint now, it supports my theory that it is number 2. There are two motors in the controllers, one with a small mass and one with a large mass. Sounds like the large mass one is stuck or broken.
 


I've just took the controller apart, and nothing was obstructing it from working. I even tested a game with it open, and there was no response. When I tested it with Dolphin, it worked fine. I'm guessing it's either a configuration/registry, OS or driver issue somewhere, or maybe a file conflicting with the configuration, I don't know, but it's not the hardware.

Official WD-40 site quote: "A Question of Lubrication

Myth: WD-40® Multi-Use Product is not really a lubricant.

Fact: While the “W-D” in WD-40® stands for Water Displacement, WD-40® Multi-Use Product is a unique, special blend of lubricants. The product’s formulation also contains anti-corrosion agents and ingredients for penetration, water displacement and soil removal."
 


A higher probability that I damaged something, but considering everything works, and the dolphin emulator successfully tests both of the motors, along with gaming inside the emulator, it's gave me reason to believe that it isn't damaged, so now it seems like it's possibly a driver issue/software. Unless a component did get damaged inside the controller that responds to a very specific frequency within different applications such as Steam, maybe. Thanks for your help!