What causes Godot controller rumble not firing?

You call start_joy_vibration with a duration of 0 expecting an indefinite buzz, or you pass the wrong joypad device index, so the motor never receives a real command.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Godot Controller Rumble Not Firing with start_joy_vibration

Quick answer: Call Input.start_joy_vibration with the correct device id and a non-zero duration, and stop it with stop_joy_vibration; on web confirm the Gamepad haptics API is supported.

When a hit should rumble but the pad stays silent, the vibration call is being ignored because of a bad argument. Passing a real device and duration fixes it. Here is how.

How to fix it

1. Use a non-zero duration

Call Input.start_joy_vibration(0, 0.7, 0.7, 0.3) with weak, strong, and duration values. A duration of 0 means continue indefinitely only if the platform supports it, and many drivers ignore it.

2. Pass the right device id

The first argument is the joypad index from Input.get_connected_joypads(), not a controller object. Hardcoding 0 fails if the active pad is on another slot.

3. Handle platform limits

HTML5 exports rely on the browser Gamepad vibrationActuator, which some browsers gate behind a user gesture. Trigger a test rumble from a button press to confirm support.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.