Haptic Design for Game Controllers: A Sound Designer's Guide

The DualSense controller is, from an audio engineer's perspective, a speaker. Not a speaker in the metaphorical sense. The voice coil actuator inside each grip is driven by an audio signal, and when the controller is connected to a PC, the operating system recognizes it as an audio output device. You can send it a sine wave at 80 Hz and it will vibrate at 80 Hz. You can send it a filtered noise burst and it will reproduce the envelope of that burst as a tactile sensation[reference:0].

This is the single most important fact for a sound designer approaching haptics. The tools you already know — EQ, filters, envelope shaping, pitch modulation — apply directly to haptic design. The parameter ranges are different, and the perceptual thresholds are different, but the underlying craft is the same.

The audio-haptic synchronization guide covers the timing relationship between sound and vibration. This article is about the other half: how to design the haptic signal itself, using the same techniques a sound designer already uses for audio.

The Actuator: What DualSense Actually Uses

The DualSense uses a voice coil actuator made by Foster Electric, mounted in each grip. The component is functionally similar to a speaker driver: an electrical signal passes through a coil, which creates a magnetic force that moves a mass attached to a spring system. The movement is what the player feels[reference:1].

The difference from a traditional rumble motor is speed. The old dual-motor design used eccentric rotating masses that took time to spin up and spin down. The attack and release were slow, which limited how precisely the vibration could be shaped. The voice coil actuator can start and stop almost instantaneously, which is what makes it possible to render a haptic waveform with the same temporal precision as an audio waveform[reference:2].

A typical voice coil actuator in this class has a resonant frequency around 70 Hz and a usable range that extends roughly from 40 Hz to 400 Hz. Outside that range, the perceived intensity drops sharply. A 20 Hz signal is mostly wasted energy; a 600 Hz signal produces almost no sensation[reference:3].

The specific figures vary between the DualSense and other controllers, but the practical lesson is consistent: the haptic actuator has a frequency response curve, just like a speaker. It is not flat. The frequencies you choose for a haptic signal determine whether the player feels anything at all.

The Frequency Range That Actually Works

The most common mistake in haptic design is sending frequencies the actuator cannot reproduce. A sound designer who is used to shaping audio in the 20 Hz to 20 kHz range will instinctively reach for low frequencies for a heavy impact. On a speaker, 50 Hz is a deep thump. On a DualSense actuator, 50 Hz is near the bottom of the usable range and produces a weak, mushy sensation.

The sweet spot is higher than most sound designers expect. The range that produces clear, strong haptic sensation on DualSense is roughly 40 Hz to 400 Hz, with the strongest response in the 80 Hz to 250 Hz band[reference:4]. This overlaps with the low-mid and mid range of audio, not the sub-bass.

The practical consequence is that haptic design requires its own frequency planning, separate from the audio frequency plan. A weapon impact sound might have its energy centered at 100 Hz in the audio mix, but the haptic version of that impact should be centered higher, somewhere in the 150 to 300 Hz range, to produce a strong tactile sensation.

The other constraint is spectral clarity. Because the usable frequency range is narrow, a haptic signal that contains many simultaneous frequencies produces a muddy, indistinct sensation. The haptics that feel clearest are the ones with a narrow spectral footprint — a single fundamental frequency, or a small number of closely spaced frequencies, with a clear envelope[reference:5].

This is the opposite of what makes a weapon sound convincing in audio. The weapon sound layering guide recommends stacking a transient, a body and a tail, each with its own spectral content. The haptic version of the same weapon should be a single, focused pulse, not a layered stack.

Authoring Haptics in a DAW

Because the DualSense actuator is an audio device, the most direct way to design haptics is in a digital audio workstation, using the same tools used for sound design.

The setup requires routing the DAW's output to both the headphones and the controller simultaneously. On Windows, this is done with a virtual audio cable such as VB-Audio Virtual Audio Cable. On macOS, LoopBack from Rogue Amoeba serves the same purpose. The DAW's output is sent to the virtual device, which is then routed to both the headphones and the controller's haptic input[reference:6].

The routing detail that catches people off guard is the channel assignment. The DualSense presents four input channels to the system, and the haptic actuators are driven by channels 3 and 4. Sending audio to channels 1 and 2 produces no vibration, because those channels are routed to the controller's built-in speaker and headphone jack, not to the actuators[reference:7].

Once the routing is correct, the design process is familiar. Create a track, load a source — a sine wave oscillator, a filtered noise burst, a recorded sample — and shape it with the same tools used for audio. A low-pass filter at 400 Hz removes the frequencies the actuator cannot reproduce. A band-pass filter around 150 Hz isolates the range that produces the strongest sensation. The amplitude envelope controls the tactile intensity over time.

The workflow advantage is that the designer can feel the haptic while hearing the audio, in real time, from the same DAW session. The two signals can be designed together, and the relationship between them can be adjusted without switching tools or exporting files.

Audio-to-Haptic Conversion: When It Works and When It Does Not

Several tools offer automatic conversion of audio to haptics. The approach is to extract the envelope of the audio signal, filter it to the haptic frequency range, and use the result to drive the actuator. This can produce usable results quickly, especially for sounds that are already low-frequency and transient-heavy.

The limitation is that audio and haptics have different perceptual requirements. A weapon sound that is rich in mid and high frequencies — which is what makes it sound sharp and impactful — will convert to a weak haptic, because those frequencies fall outside the actuator's range. The conversion produces a haptic that is technically derived from the sound but perceptually disconnected from it.

The practical fix is a two-stage process. The conversion handles the envelope and the timing, and a second stage synthesizes a low-frequency signal that fills the actuator's usable range. The result is a haptic that shares the rhythm and dynamics of the sound while having its own spectral content designed for the actuator.

For sounds that are already centered in the low-mid range — a heavy footstep, a deep impact, a low-frequency rumble — direct conversion works reasonably well. For sounds that are bright and transient-heavy, the synthesized low-frequency layer is essential.

Wwise Motion: The Middleware Approach

For projects that already use Wwise for audio, the Motion plugin provides a path to haptics that fits the existing middleware workflow. The setup is a parallel structure to the audio bus system.

A Motion Bus is created in the Master Mixer Hierarchy and assigned to a Wwise Motion Audio Device. A Sound SFX object is routed to that bus, and a Motion Source is used as its source. The Motion Source can be a synthesized waveform, a converted audio signal, or a native haptic clip. When the event is played, the haptic signal is sent to the controller through the same event system that handles audio[reference:9].

The preview workflow in Wwise Authoring allows the designer to feel the haptic on a connected DualSense while playing the event in the editor. The Motion Bus audio device is set to the DualSense, and the event is played as it would be in the game[reference:10].

The integration into the game requires an output device registration. In Unreal, this is handled by calling AddOutput on the PlayerController when a gamepad is connected, or by responding to the OnInputDeviceConnectionChange callback. The Motion signal is then routed to the connected controller alongside the audio output[reference:11].

The advantage of the Wwise approach is that haptics become part of the audio event system rather than a separate system. The same randomization, the same switches, the same RTPCs that control audio can control haptics. A weapon that changes its sound based on upgrade level can change its haptic in the same way, through the same event.

Design Principles That Carry Over from Audio

The craft of haptic design is not a separate discipline. It is audio design applied to a different output device. The principles that make a good sound effect are the same principles that make a good haptic.

Attack matters more than sustain. A haptic that starts immediately is perceived as more impactful than one that fades in, regardless of peak intensity. The transient is the moment of contact, and the actuator's ability to start instantly is what makes that moment readable.

Decay should match the physical metaphor. A metal impact rings; a cloth impact does not. The haptic decay should mirror the decay of the sound and the visual. A cloth impact with a long haptic tail feels wrong, because the haptic is communicating a material property that the visuals contradict.

Variation prevents fatigue. The same haptic pulse repeated identically every time becomes noticeable in the same way a repeated sound does. Small random variations in intensity and timing keep the haptic feeling natural. This is the same principle behind footstep variation and coin sound variation.

Silence is part of the design. A haptic that fires for every event becomes noise. The events that do not need haptics — ambient sounds, music, UI navigation — should stay silent. The contrast between haptic and non-haptic events is what gives the haptic meaning.

The haptic and the sound should agree. If the sound is a sharp crack and the haptic is a soft rumble, the player's brain receives conflicting information about what happened. The haptic intensity should scale with the sound intensity, and the haptic character should match the sound's spectral character within the limits of the actuator.

Testing Haptics: What to Listen For with Your Hands

Haptic testing is different from audio testing because the feedback is felt rather than heard. The evaluation criteria are also different.

The first test is strength at the target frequency. Play the haptic signal in isolation with no audio. Can you feel it clearly? If the sensation is weak or mushy, the dominant frequency is outside the actuator's sweet spot. Move it up or down in 20 Hz increments until the sensation is strongest.

The second test is clarity. Play the haptic signal repeatedly. Does it feel like one distinct pulse, or does it blur into a continuous buzz? A haptic that blurs is either too long or has too much spectral content. Narrowing the frequency range and shortening the decay will sharpen it.

The third test is synchronization with the sound. Play the sound and the haptic together. Do they feel like one event? The synchronization guide covers the timing thresholds; the subjective test is whether you perceive one sensation or two.

The fourth test is repetition. Trigger the effect twenty or thirty times in a row. Does it remain comfortable, or does it become irritating? A haptic that is pleasant once can become fatiguing after repeated exposure, especially if it is strong and high-frequency.

The final test is accessibility. Turn the haptics off entirely. Does the game still communicate everything it needs to? If the answer is no, the haptic is carrying information that should also be present in the audio or visual channels. Haptics should supplement, not replace.

Common Mistakes

• Using sub-bass frequencies. A 40 Hz sine wave feels weak on a DualSense actuator. The strongest response is in the 80 to 250 Hz range.
• Designing haptics as a separate discipline. The tools are the same as audio. A sound designer already knows how to shape an envelope and filter a signal. The only new information is the actuator's frequency response and the perceptual thresholds.
• Using the wrong channels. The haptic actuators are driven by channels 3 and 4, not channels 1 and 2. Sending audio to the wrong channels produces no vibration.
• Making every haptic strong. A haptic that is always at maximum intensity leaves no room for contrast. The strongest haptics should be reserved for the most important events.
• Ignoring spectral clarity. A haptic with many simultaneous frequencies feels muddy. Narrow the spectral range to a single dominant frequency or a small cluster.
• Forgetting the accessibility requirement. A game that cannot be played without haptics fails for players who have disabled vibration. The haptic must supplement other feedback channels.

How to Decide Which Events Deserve Haptics

Not every sound needs a haptic partner. The events that benefit most are the ones where the player's body is supposed to be involved in the game world.

The strongest candidates are impacts and collisions, weapon fire and recoil, damage taken, state changes the player needs to notice, and mechanical interactions like levers and switches. These are the moments where the tactile channel reinforces the physical fiction of the game.

The events that do not need haptics are ambient sounds, music, UI navigation, and anything that plays continuously or frequently enough to become fatiguing. A haptic that fires on every menu click is a haptic the player will disable within the first session.

The general rule is to start with silence and add haptics only where they add something the audio and visual channels cannot. A haptic that is felt is a haptic that is doing its job. A haptic that is noticed as a separate thing is a haptic that is doing too much.