Skip to main content
Programmatic Suite

Haptic Composer: Explosion (Unreal)

Design and test an interactive explosion haptic feedback rumble pattern. Export production-ready C# code for Unreal game developers directly to your clipboard.

Haptic Waveform unreal

Waveform Composer

Drag points to sculpt your rumble curve. X = Time (ms), Y = Intensity (0-100%).

INTENSITY (Y) ↑ TIME (1000MS) →

Unreal Engine (C++) Output

Implementation Guide

Follow the generated code snippet to integrate this haptic waveform into your game. Ensure you have the required input management packages installed for Unreal.

How to Get Started

Just three steps to run a complete controller test and understand your controller's health status.

01

Connect Controller

Connect your controller to your computer via USB cable or Bluetooth. If the browser doesn't respond, press any button on the controller to activate the connection.

02

Button Detection

Press each button in the visual interface and confirm the corresponding area lights up on screen. This helps troubleshoot unresponsive or double-clicking buttons.

03

Sticks & Vibration

Rotate the sticks to check linearity and drift issues; click the vibration test button to feel if the left and right motor feedback is working properly.

What would you like to do next?

Select a diagnostic calibration suite, deadzone analyzer, or high-frequency overclock tool.

Fix

Repair & Calibration

Calibrate zero-point offsets or follow step-by-step repair guides.

Optimize

Game Deadzones

Calculate exact radial vs axial deadzone overlays for Fortnite, Apex, & COD.

Telemetry

Overclock & Circularity

Verify browser-observed update timing Hz stability and statistical circularity grades.

Designing explosion Haptics in Unreal

A well-designed explosion rumble pattern reads as an impact: a sharp, strong-motor attack spike that decays quickly, with a low-frequency tail that carries the pressure wave. The reason this shape works is that the first 50–100ms sell the hit; the decaying tail keeps the effect readable without overpowering the game audio.

When to use it: pair it with the actual audio explosion cue — the tactile peak should land on the audio transient, not slightly before or after. Tuning notes: Explosions are the hardest effect to tune because they fight the game audio for attention. The classic failure is an over-long tail that muddies the next cue; the fix is to cut the decay before the rumble becomes a drone. On real controllers, the strong motor carries most of the pressure wave while the weak motor should stay quiet or pulse once at the moment of detonation — giving both motors a full-strength tail is the most common reason an explosion feels like a vibration rather than a hit.

Engine integration

In Unreal, Unreal plays pre-authored haptic assets via PlayHapticEffect; for procedural curves, update the motor speed each tick from your own curve sample rather than a fixed pattern. For the explosion pattern specifically, author the {effect} envelope as a float curve asset so designers can tune the shape without touching code. Unreal's PlayHapticEffect is asset-driven and efficient at runtime, but the asset pipeline is where designers actually tune feel — so expose the {effect} amplitude and duration as curve keys and let the gameplay team iterate on them in-editor rather than recompiling code each time the feel changes.

Unreal bakes feel into content assets rather than code: a {effect} envelope authored as a CurveFloat is a gameplay asset that designers own, which means amplitude, duration and attack can be tweaked in the editor and hot-reloaded while the game runs on a controller. PlayHapticEffect plays those assets on the active device automatically, and you layer them with the feedback system's triggers if you want the effect gated by gameplay events. The cost of the asset pipeline is iteration speed — a code-driven curve gives you a live loop, while an asset forces a re-import — so for a first draft of an explosion, prototype the envelope in Blueprint, then bake the winner into a curve asset for shipping.

Haptic feedback bridges the gap between digital interaction and physical sensation. Matching the visual and auditory cues with the tactile response is what makes the effect feel intentional rather than decorative.

Controller Hardware Glossary & Tips

Stick Drift & Deadzones

Stick drift occurs when analog sticks register input without being touched. This is typically caused by physical wear in traditional carbon-film potentiometers. A deadzone is a software-level threshold (e.g., 5-10%) applied to ignore these microscopic false inputs.

Hall Effect Sensors

Unlike traditional ALPS potentiometers, Hall Effect modules use magnetic fields to measure stick position. Because there is no physical contact or friction between the internal components, they are virtually immune to wear-induced stick drift, drastically extending the controller's lifespan.

Polling Rate (Hz) & Input Latency

Polling rate is how often your controller sends data to your device, measured in Hertz (Hz). A standard Bluetooth connection yields around 125Hz (8ms latency). Overclocking or using a wired USB connection can push this to 500Hz-1000Hz (1ms-2ms latency), critical for competitive gaming.

Circularity Error

When you rotate a joystick along its outer edge, a perfect module should trace a mathematically perfect circle. Circularity error measures the deviation from this perfect circle. High deviations (>15%) can result in uneven diagonal movement speeds in FPS games.

Frequently Asked Questions

Everything you need to know about testing your controller.

How do I use this explosion rumble pattern in unreal?

Simply adjust the waveform curve to your liking, test it live using your connected controller, and copy the generated C# script from the panel below into your unreal project.

Does the Web Gamepad API support complex rumble curves?

The Web Gamepad API primarily supports standard dual-rumble (weak and strong motors). To simulate complex curves like this tool does, we play multiple sequential rumble effects over short durations. Game engines support richer curve evaluation natively.

How this test works & its limits
  • This test reads your controller through the browser's standard Gamepad API — no drivers, no installs, nothing leaves your device.
  • Readings depend on connection mode: Bluetooth reports at lower rates than USB. Compare like-for-like (wired vs wired).
  • We measure the input reaching the browser — display lag and game-engine queues are outside this test's view.
  • A clean reading now does not guarantee no drift in-game: deadzones differ per game, and wear develops over time. Use the Drift Timeline to track yours.
  • This is a diagnostic, not a hardware-lab certification. For repair or RMA decisions, confirm with a second run or second tool.
Read the full methodology
100% Client-Side

All Gamepad API data stays in your browser. Zero tracking or data collection.

Instant Results

No downloads, plugins, or software installation needed. Works instantly.

Free Forever

No paywalls, subscription requirements, or hidden usage limits.