Guide

Game haptics and rumble explained

Players feel your game through their hands before they consciously register what happened on screen. A crisp landing thump, the resistance of a bow at full draw, the buzz of low health — haptics translate game state into physical sensation. Done well, rumble extends juice and feel into the controller; done poorly, it becomes a constant annoyance players disable in settings. This guide covers impulse vs continuous vibration, platform APIs from the Web Gamepad API to PlayStation DualSense adaptive triggers, haptic design tiers, layering and priority, ties to audio and input, mobile Taptic Engine patterns, accessibility, and production pitfalls.

What haptics are — and what rumble is not

Haptics is the broad category of tactile feedback: vibration motors, force-feedback wheels, phone Taptic Engines, and resistance-based triggers. Rumble usually means eccentric rotating mass (ERM) motors inside a gamepad — cheap, loud, and imprecise compared to linear resonant actuators (LRA) or voice-coil drivers in modern controllers.

Three axes define your haptic stack:

Actuator type — ERM rumble (legacy Xbox/PlayStation), HD haptics (Switch Joy-Con, DualSense), or mobile LRA/Taptic.
Signal shape — one-shot impulses (hit confirms), sustained loops (engine idle), or parameterized curves (draw strength).
Semantic role — confirmatory (button press), informational (damage direction), or atmospheric (rain on a roof).

Haptics are not a substitute for clear visuals or SFX. They reinforce events the player already understands. If the screen does not communicate "you were hit," no amount of rumble will fix confusion — it will only add noise.

Platform APIs and hardware capabilities

Web and generic gamepads

The Gamepad API exposes gamepad.vibrationActuator on supporting browsers (primarily Chromium). You call playEffect("dual-rumble", { duration, strongMagnitude, weakMagnitude }) for left/right motor control. Capabilities vary wildly: many Bluetooth pads ignore vibration in browser builds, and Safari support lags. Treat web haptics as a progressive enhancement, never a required mechanic.

PlayStation DualSense and DualShock

Sony's DualSense adds high-definition actuators plus adaptive triggers — variable resistance on L2/R2 via geared mechanisms. Native SDKs let you set trigger modes: off, feedback (resistance ramps with pull distance), or weapon (detents and release snaps). Haptic audio samples can drive the actuators for textured sensations (rain, footsteps on glass). DualShock 4 offers simpler dual-motor rumble without adaptive triggers.

Xbox and PC

Xbox controllers use traditional dual ERM motors. The Xbox GDK and XInput expose XInputSetState with 16-bit left/right motor speeds. Impulse Trigger motors on Xbox One-era pads are largely underused. On PC, Steam Input remaps and can inject rumble on behalf of games that lack native support — but profiles differ per device, so test on hardware, not emulators alone.

Nintendo Switch

Joy-Con HD Rumble uses linear actuators capable of fine frequency control — famously demonstrated with a "virtual ice cube" rolling inside the controller. The Switch SDK exposes amplitude and frequency per side. Handheld vs docked does not change actuator behavior, but grip style (single Joy-Con vs Pro Controller) changes perceived intensity.

Mobile touch haptics

iOS Core Haptics and Android VibrationEffect support transient taps, continuous waves, and predefined patterns. Mobile games often use light taps for UI confirms and heavier pulses for damage — but over-vibration drains battery and annoys players in public. Always respect the system "disable vibration" setting and offer an in-game toggle.

Haptic design: tiers, timing, and localization

Intensity tiers

Borrow the same philosophy as graded screen shake: define three to five tiers (micro, light, medium, heavy, critical) mapped to gameplay events. A UI hover should never use the same motor curve as a boss slam. Document tiers in a spreadsheet alongside your SFX loudness ladder so audio and haptics stay coherent.

Impulse envelopes

Raw "motor on for 200 ms" feels mushy. Shape impulses with attack, sustain, and decay — even if the API only accepts duration and magnitude, simulate envelopes by chaining short segments or modulating magnitude over time. Sharp 30–50 ms spikes sell impacts; long flat rumble reads as "something is broken."

Directional and spatial haptics

With dual motors, pan intensity left/right to hint damage direction. Pair with stereo audio panning for multimodal consistency. For top-down games, directional rumble matters less than rhythm — heartbeat pulses during low health work because they repeat predictably, not because they indicate bearing.

Sync with animation and audio

Fire haptics on the same frame as hit-stop and the transient SFX attack. A 16 ms delay between visual freeze and rumble is noticeable; 50 ms feels broken. In networked games, trigger local haptics on client prediction for your own actions; for incoming damage, sync to the authoritative hit confirm event to avoid double pulses on rollback.

Architecture: haptic manager, layering, and priority

Scattershot rumble(0.8) calls across gameplay code become unmaintainable. Centralize through a haptic manager that:

Loads preset definitions (JSON or ScriptableObjects) keyed by event ID.
Resolves platform at runtime — DualSense trigger effect vs fallback dual-rumble.
Supports priority and interruption — a critical hit cancels ambient road vibration; ambient loops duck rather than stack.
Respects global mute, per-category toggles (combat / UI / ambient), and accessibility reduced-feedback modes.

Layer at most two simultaneous effects: one ambient (engine, storm) and one foreground (combat). Three or more overlapping motors feel like static and wash out semantic meaning. Queue short impulses rather than stacking them when the player lands ten hits per second — merge into a single stronger pulse with cooldown.

Adaptive triggers and advanced patterns

Adaptive triggers shine when resistance is the mechanic: drawing a bow, charging a shot, driving over terrain, or a car handbrake with progressive bite. Map trigger position to game state each frame; release resistance to zero on the exact frame of discharge for a satisfying snap. Avoid leaving residual resistance after state exit — players will think the controller is faulty.

Do not gate core gameplay behind trigger hardware. Always provide equivalent input on standard buttons for Xbox, keyboard, and accessibility remaps. Adaptive triggers are enhancement, not requirement.

Accessibility and player comfort

Vestibular and sensory sensitivities extend to hands and arms. Long high-intensity rumble causes fatigue and can trigger discomfort for players with certain neurological conditions. Provide:

A master haptics off toggle (separate from audio mute).
Per-category sliders: combat, environment, UI.
Reduced-intensity preset that scales all magnitudes by 50%.
No haptic-only information — never encode puzzle solutions or enemy positions solely in vibration.

Follow platform certification checklists (Xbox XR, PlayStation TRC) which often mandate rumble-off behavior and maximum continuous duration limits.

Common anti-patterns

Constant ambient rumble — players disable all feedback; use sparse texture instead.
Identical pulses for every event — UI click and explosion feel the same; tiers exist for a reason.
Ignoring battery and heat — mobile and Switch handheld modes suffer from aggressive motors left on.
Web-only testing — browser Gamepad vibration is not representative of console feel.
Haptics without audio/visual partners — orphaned rumble confuses more than it informs.
No cooldown on rapid events — machine-gun fire becomes a buzzing mess; aggregate or skip pulses.

Decision table: when to use which pattern

Event type	Pattern	Duration	Notes
UI confirm	Single micro impulse	10–25 ms	Match system tap on mobile; optional on desktop
Light hit	Sharp medium impulse, slight L/R pan	40–80 ms	Sync with hit-stop and SFX transient
Heavy impact / death	Strong dual pulse + decay	100–200 ms	One-shot; cancel ambient layers
Charged ability	Rising magnitude or adaptive trigger ramp	While held	Release to zero on fire frame
Low health warning	Rhythmic pulse loop	1–2 Hz repeat	Stop immediately on heal; pair with vignette
Vehicle / engine idle	Low continuous, low frequency	While active	Duck under combat; disable when paused

Production checklist

Central haptic manager with named presets and platform fallbacks defined.
Intensity tier doc aligned with SFX and camera shake ladders.
Impulse envelopes shaped — no flat 500 ms blobs for hits.
Priority/interrupt rules: combat overrides ambient; UI never blocks critical.
Adaptive trigger effects implemented with standard-button fallback.
Master off + per-category sliders in accessibility settings.
No haptic-only critical information for puzzles or combat telegraphs.
Cooldown or merge logic for high-frequency events (full auto, DOT ticks).
Pause/menu zeroes all motors and trigger resistance immediately.
Hardware test matrix: DualSense, Xbox pad, Switch Pro, mobile, browser.
Battery profile check on handheld after 30-minute stress session.
Certification requirements (TRC/XR) reviewed for rumble duration caps.

Key takeaways

Haptics reinforce, they do not teach — pair with clear visuals and audio every time.
Tier and shape impulses — micro UI taps and boss slams should never share the same curve.
Centralize through a manager with priority, layering limits, and platform abstraction.
Adaptive triggers are optional enhancement — never block gameplay on proprietary hardware.
Accessibility is mandatory — full off toggle, category controls, and no haptic-only information.