-
Notifications
You must be signed in to change notification settings - Fork 6
Force Feedback
The Force Feedback tab controls rumble and vibration — adjust overall strength, balance each motor, test feedback, or generate vibration from system audio.

Most controllers have two vibration motors:
| Motor | Character | Typical Use |
|---|---|---|
| Left (low-frequency) | Heavy, deep thump | Explosions, collisions, engine vibration |
| Right (high-frequency) | Light, sharp buzz | Gunfire, road texture, UI feedback |
Games blend both motors for varied effects. A wall collision might slam the left motor while gently buzzing the right for debris. A machine gun might pulse the right motor rapidly while leaving the left idle.
Games never talk to your physical controller directly. The signal path is:
- Game sends rumble to PadForge's virtual controller (Xbox 360, DualShock 4, or DirectInput).
- PadForge receives the left and right motor values.
- Your settings are applied — gain, per-motor strength, motor swap.
- PadForge forwards the adjusted rumble to your physical controller.
This runs at PadForge's polling rate (typically hundreds of times per second), so feedback feels instantaneous.
When one physical controller is assigned to multiple virtual slots, PadForge takes the highest motor value from any active slot. No rumble signals are lost.
| Setting | Range | Default | Description |
|---|---|---|---|
| Overall Gain | 0–100% | 100% | Master vibration strength. Scales both motors equally before per-motor adjustment. 0% disables rumble entirely. |
| Left Motor | 0–100% | 100% | Low-frequency motor strength. Reduce if deep rumble feels too strong. |
| Right Motor | 0–100% | 100% | High-frequency motor strength. Reduce if the buzzy vibration is distracting. |
| Swap Motors | On/Off | Off | Reverses which physical motor receives left vs. right signals. Useful for controllers with non-standard motor layouts or games whose rumble feels backwards. |
Click Test Rumble to send a short vibration pulse to your physical controller. This confirms:
- Your device supports rumble
- PadForge is forwarding feedback correctly
- Your gain and motor settings produce the desired effect
When multiple physical devices share a slot, the test pulse targets only the device you are configuring.
The real-time Motor Activity bars display current vibration intensity for each motor as games send rumble commands — left bar for low-frequency, right bar for high-frequency.
Use the bars to:
- Observe which motor a game favors and how intense its signals are
- Tune strength settings by watching how adjustments scale the live output
- Confirm audio bass rumble is adding vibration when expected
Some devices — racing wheels, arcade sticks, flight sticks — lack traditional rumble motors but support haptic force feedback. PadForge detects these automatically and translates rumble into haptic effects.
PadForge selects the best available strategy in priority order:
| Priority | Strategy | Behavior |
|---|---|---|
| 1st | Left/Right effects | Two independent vibration channels — closest to dual-motor rumble |
| 2nd | Sine wave effects | Periodic vibration. Period varies by dominant motor: slow oscillation for heavy, fast buzz for light. |
| 3rd | Constant force effects | Steady force matching the strongest motor signal. Less nuanced, but still provides feedback. |
No configuration needed. If a device supports neither rumble nor haptics, PadForge skips vibration for it.
For haptic devices (wheels, joysticks), PadForge preserves force direction rather than collapsing it to a single value:
- Joysticks with two or more haptic axes receive true 2D directional forces — a leftward force produces stronger feedback on the left side.
- Racing wheels with a single axis receive forces projected onto the steering axis — a rightward force pushes the wheel clockwise, leftward pushes counterclockwise.
Directional forces apply to constant, ramp, and all periodic effect types (sine, square, triangle, sawtooth up/down). If a device does not support a requested effect type, PadForge falls back to scalar rumble.
Condition effects are position- or velocity-dependent forces used in racing and flight simulators. Unlike constant rumble, they react dynamically to how you move your controller or wheel.
| Effect | Feel | Common Use |
|---|---|---|
| Spring | Centering force — stronger the farther you push from center | Steering wheel self-centering, joystick return-to-neutral |
| Damper | Speed-dependent resistance — slow feels smooth, fast feels heavy | Hydraulic steering simulation |
| Friction | Constant resistance in any direction | Road surface feel, mechanical friction |
| Inertia | Resistance to speed changes — hard to start, hard to stop | Heavy steering column or flight yoke mass |
Overall Gain scales condition effect intensity. These effects work best with force feedback wheels and joysticks. Standard gamepads receive them as simplified rumble.
When a slot uses DirectInput output, force feedback flows through the DirectInput pipeline:
- Games send DirectInput effects (constant force, sine, ramp, sawtooth, and more) to the virtual DirectInput device.
- PadForge translates them into rumble or haptic commands for your physical controller.
- All settings — Overall Gain, per-motor strength, Swap Motors — apply normally.
The virtual DirectInput device advertises full force feedback capability. DirectInput games discover and use it automatically.
PadForge generates controller vibration from any system audio — games, music, video. It captures audio via Windows loopback, isolates bass frequencies with a steep 48 dB/octave low-pass filter, and converts bass energy into motor speed values. The result is vibration that pulses in sync with bass-heavy sounds.
Audio bass rumble combines with game rumble — PadForge uses whichever signal is stronger at any moment. Audio rumble fills gaps during cutscenes, menus, or quiet gameplay where native rumble is absent.
PadForge follows your default audio output device automatically. Switching from speakers to headphones requires no reconfiguration.
- Open the Force Feedback tab for the desired controller slot.
- Check Enable Audio Rumble.
- Adjust sliders while audio plays and watch the Level meter to fine-tune.
| Setting | Range | Default | Description |
|---|---|---|---|
| Sensitivity | 1.0–20.0 | 4.0 | Bass intensity multiplier. Higher = stronger rumble from quieter audio. |
| Bass Cutoff | 20–200 Hz | 80 Hz | Low-pass filter cutoff. Lower values isolate deep sub-bass only; higher values include more of the bass range. |
| Left Motor | 0–100% | 100% | Audio-driven scale for the low-frequency motor. |
| Right Motor | 0–100% | 100% | Audio-driven scale for the high-frequency motor. |
The real-time Level meter shows current bass energy as audio plays.
| Scenario | Sensitivity | Bass Cutoff | Notes |
|---|---|---|---|
| Action games without native rumble | Default (4.0) | Default (80 Hz) | Increase sensitivity if rumble feels subtle |
| Music listening | 6–8 | 100–150 Hz | Picks up kick drums and bass guitar. Reduce right motor to 50% for deeper feel. |
| Movies and video | Default | 40–60 Hz | Isolates deep cinematic rumble — thunder, explosions, LFE |
| Racing games with weak rumble | Default | 40–60 Hz | Adds engine rumble and collision impacts from the game's audio |
| Horror / atmospheric games | 2–3 | 30–50 Hz | Subtle vibrations from ambient bass drones |
Each slider has an individual reset button that restores its default value. The Reset All button restores all settings in its section:
- Rumble Reset All — Overall Gain 100%, both motors 100%, Swap Motors off
- Audio Rumble Reset All — Audio rumble disabled, sensitivity 4.0, cutoff 80 Hz, both motors 100%
- Start with defaults. 100% gain and 100% both motors passes through exactly what the game sends. Only reduce if vibration feels too intense.
- Use the motor activity bars for tuning. Watch them during gameplay to see how a game uses each motor, then adjust accordingly.
- Lower the right motor for less buzz. Reducing to 60–80% keeps deep thumps while softening the high-frequency buzz many players find distracting.
- Tune during gameplay, not just with Test Rumble. Real games use varied, dynamic patterns that the test pulse cannot replicate.
- Audio rumble works alongside game rumble. Enable it even in games with native feedback — it only activates when bass exceeds the game's own signal.
- Each device gets independent settings. Tune force feedback per controller on each slot.
- Use DirectInput output for racing wheels. Wheels benefit most from condition effects and directional forces — features only available through the DirectInput pipeline.
| Problem | Solution |
|---|---|
| No vibration at all | Verify Overall Gain is above 0%. Click Test Rumble to confirm device support. |
| Vibration too weak | Increase Overall Gain and per-motor strength sliders. |
| Vibration too strong | Decrease Overall Gain or reduce individual motor strength. |
| Rumble feels reversed | Enable Swap Motors. |
| Rumble stops intermittently | Ensure no other software (e.g., Steam Input) is competing for vibration control. |
| Audio rumble not working | Confirm audio plays through your default output device. Check Level meter activity. Increase sensitivity if the meter barely moves. |
| Audio rumble too aggressive | Reduce sensitivity or lower the bass cutoff. |
| Wheel force feedback feels wrong | Use a DirectInput output slot for your wheel — not Xbox 360 or DualShock 4. |
| Condition effects feel weak | Increase Overall Gain. Condition effects scale with this setting. |
- Button and Axis Mappings — Map your controller's inputs
- Trigger Dead Zones — Pair trigger adjustments with rumble tuning
- Troubleshooting — More help with rumble issues