How Gaming Controllers Create Precise Vibration Feedback

How Gaming Controllers Create Precise Vibration Feedback

You're mid-chase. The controller in your hands shudders with a low, rolling groan as the engine revs, then cracks sharp when the bumper clips a barrier, then buzzes in a long, greasy slide as the tires let go. None of that is coming from the screen. It's coming from two small motors bolted inside a plastic shell, and the engineering behind it is a lot weirder and more elegant than most people realise.

Two Dumb Motors Doing Something Smart

Strip a standard rumble controller down to its guts and you'll find an eccentric rotating mass motor, or ERM, on each side. The concept is almost embarrassingly simple: a small electric motor with an unbalanced weight on its shaft. When the motor spins, the off-centre mass creates centrifugal force that wobbles the whole housing. That wobble is the vibration you feel.

The two motors are intentionally different sizes. The one on the right is small and fast, producing a high-frequency buzz, roughly 50 to 130 Hz in most designs. The one on the left is heavier and slower, grinding out a low-frequency rumble closer to 10 to 40 Hz. Neither motor, on its own, is doing anything sophisticated.

The sophistication comes from what the console tells them to do and when. Game code sends each motor an independent duty cycle: a number between 0 and 65,535 in the Xbox input API, representing how hard each side should spin. The console's haptics driver converts that number into a pulse-width modulation signal, basically a rapid on/off current that averages out to the desired power level. Higher duty cycle, faster spin, stronger vibration. The motor doesn't know it's simulating a gunshot. It's just spinning at a speed it was told to spin at.

The Part Most Guides Skip

Here's the wrinkle that makes this interesting: the motors have rotational inertia. Spin one up fast and then cut the signal to zero, and it doesn't stop instantly. It coasts. That coasting is a problem when you want a tight, percussive tap rather than a smear of vibration that lingers for half a second.

Engineers work around this in a few ways. One approach is active braking: briefly reversing the current through the motor to kill its momentum faster, the same principle that makes electric cars stop so sharply. Another is designing the timing of feedback events to account for spin-up and spin-down lag, firing the signal slightly early so the peak vibration lands when the on-screen event actually happens.

This is the gap between a well-tuned haptic effect and a sloppy one. A developer who ignores motor inertia gets a controller that feels like it's always slightly behind the action. A developer who models it correctly gets that satisfying crack-and-stop when a sniper shot lands. Most players can't articulate the difference. They just know one feels cheap.

When the Technology Levelled Up

The DualSense controller moved away from ERMs entirely in favour of linear resonant actuators, or LRAs. Instead of a spinning weight, an LRA uses an electromagnetic coil to push a small weighted plate back and forth along a single axis. Think of it less like a washing machine on spin cycle and more like a tiny speaker cone that never makes sound, just motion, with all its energy pointed directly at your palms.

LRAs respond in roughly 5 to 10 milliseconds, compared to the 50-plus milliseconds it takes an ERM to spin up to meaningful speed. They can also target specific resonant frequencies with much greater precision, which is why the DualSense can convincingly simulate the texture of gravel under tires versus the snap of a bowstring. The controller is essentially playing a haptic waveform the same way a speaker plays an audio waveform.

Sony went a step further and put independent LRAs under each trigger, allowing the L2 and R2 buttons to resist your finger at programmable points in their travel. Pull the trigger in a racing game and it stiffens as the tires lose traction. That's not magic. It's a small motor pushing back against a mechanical lever, controlled by the same duty-cycle logic, just applied laterally instead of to the whole housing.

What People Get Wrong About Haptics

The folk wisdom that more vibration equals better haptics needs to die. Intensity is the least interesting axis, and any designer who leads with it is telling you they don't understand the tool.

Consider two developers given identical hardware. One maps every in-game event to a single full-power buzz lasting 200 milliseconds. The other uses the high-frequency motor for UI confirmations (a short 80 Hz pulse, maybe 30 milliseconds), the low-frequency motor for environmental weight (a 20 Hz rumble that fades over 400 milliseconds as an explosion dissipates), and goes completely silent during menus. After an hour, the first controller feels like a blunt instrument. The second feels like part of the game.

The brain is remarkably good at filtering out constant vibration. Same reason you stop noticing a car's engine hum after ten minutes on a motorway. Haptic feedback that runs too often or too uniformly trains your nervous system to ignore it. The silence between effects is load-bearing.

A Tale of Two Players

Take two people who buy the same racing game on the same console. Maya leaves every haptic setting at default. Within twenty minutes, she's using the steering feedback to feel the difference between tarmac and a gravel runoff area, modulating her braking before she consciously registers the visual cue. Carlos, who finds vibration distracting, turns it off in the first settings menu he finds.

A month later, Carlos is faster in qualifying laps, where the track is clean and predictable. Maya is faster in wet races, where grip is inconsistent and the visual information arrives a half-second too late to act on.

Neither is wrong. But here's the question worth sitting with: when did you last treat a controller's feedback as actual information rather than atmosphere? Maya is using a genuinely different information channel, one that runs through the skin rather than the eyes, and it's doing real cognitive work. That's not immersion as a marketing word. It's a second sensory pipeline carrying game state that your eyes don't have bandwidth to process alone.

The two spinning motors in a basic rumble controller were always pointing at that idea. The newer hardware just finally has the precision to make good on it.