Your quad feels mushy on sharp stick inputs even with perfect PIDs. That disconnect between your thumb and the quad’s response? That’s where feed forward steps in. Configure it correctly and you get instant, precise stick tracking without overshoot — get it wrong and you’ll chase oscillations all day.
What Feed Forward Actually Does
Feed forward is a predictive term added to the PID controller. Unlike P, I, and D — which all react to errors that have already happened — feed forward looks at your stick movement and directly adds motor output proportional to how fast you’re moving the stick. It bypasses the error loop entirely.
In Betaflight 4.3 and later, feed forward has two tunable parameters:
Feed Forward (ff)
The primary gain. At ff = 100, the controller predicts and applies 100% of the expected motor output change from your stick movement. At ff = 0, it’s disabled entirely and you rely solely on P-term for stick tracking.
Feed Forward Smoothing (ff_smooth_factor)
Introduced in Betaflight 4.4. This low-pass filter smooths the feed forward signal to prevent noise amplification. Lower values = more smoothing = softer response. Higher values = less smoothing = sharper response with risk of jitter.
Step-by-Step Feed Forward Tuning
Step 1: Baseline Your PIDs First
Feed forward amplifies your existing tune. If your P-term is already too high and causing oscillation, feed forward will make it worse. Start with a clean, conservative PID tune:
– Set ff = 0 temporarily
– Tune P, I, and D to be clean — no oscillations in punch-outs, propwash, or hard turns
– Once stable, proceed to feed forward
Step 2: Set Initial Feed Forward Values
For most 5-inch freestyle quads:
– Roll/Pitch: ff = 80 is a safe starting point
– Yaw: ff = 90 (yaw benefits from higher feed forward due to slower axis response)
– ff_smooth_factor = 37 (4.4+ default)
For racing builds (lightweight, high power-to-weight): start at ff = 60 — these quads are already responsive and too much feed forward causes twitchiness.
For heavy cinematic rigs (GoPro, 7-inch): start at ff = 100 — these need maximum stick authority.
Step 3: Flight Test — Sharp Stick Deflections
Fly aggressive snap rolls and flips. Watch for these symptoms:
– Oscillation on sharp stops: Feed forward too high. Drop by 10.
– Mushy, delayed response: Feed forward too low. Increase by 10.
– Jittery, nervous feel in hover: ff_smooth_factor too high. Reduce it by 10.
– Still mushy but ff is at 100: Check your rates — if your RC rate is very low, there’s simply less stick movement for feed forward to work with.
Step 4: Adjust Feed Forward Smoothing
After finding your ideal ff values, fine-tune ff_smooth_factor:
– If the quad reacts instantly but feels “grainy” or jittery on small corrections, reduce ff_smooth_factor to 25-30
– If response is too soft and you want more directness, increase to 45-50
– Racing pilots often run ff_smooth_factor = 50-60 for maximum immediacy
– Freestyle pilots typically land at 30-40 for controllable snap without nervousness
Step 5: Verify with Blackbox
The definitive check: log a flight with sharp stick inputs. In the Blackbox viewer, overlay rcCommand[roll] with gyro[roll]. With well-tuned feed forward, the gyro trace should track the rcCommand trace almost perfectly — minimal lag, minimal overshoot.
Feed Forward Parameter Reference
| Setting | Range | Racing Start | Freestyle Start | Cinematic Start | Too High Symptom | Too Low Symptom |
|---|---|---|---|---|---|---|
ff (roll/pitch) |
0-255 | 60-80 | 80-100 | 90-120 | Oscillation on stops | Mushy stick feel |
ff (yaw) |
0-255 | 80-100 | 90-110 | 100-130 | Yaw bounce on stop | Slow yaw authority |
ff_smooth_factor |
0-75 | 40-60 | 30-40 | 25-35 | Jittery/nervous feel | Sluggish response |
ff_interpolate |
ON/OFF | ON | ON | ON | N/A (keep on) | Step-like response |
What Most Pilots Get Wrong
Mistake 1: Cranking Feed Forward Before Fixing PIDs
Pilots chase stick feel by maxing out feed forward when their P-term is the real problem. Feed forward masks a bad tune but creates oscillation under load. Fix: Always lower feed forward to zero and tune PIDs clean first. Feed forward is seasoning — it doesn’t fix bad ingredients.
Mistake 2: Running the Same Feed Forward on All Profiles
Your 5-inch freestyle tune at ff = 90 will make a 3-inch toothpick completely unflyable. Smaller quads have lower inertia and need less feed forward. Fix: Tune feed forward per-build, not per-pilot. A 3-inch whoop might need ff = 50 while a 7-inch cruiser needs ff = 120.
Mistake 3: Ignoring Feed Forward Smoothing Entirely
Betaflight 4.4+ pilots set ff and never touch ff_smooth_factor. On default firmware, the smoothing is conservative and your expensive feed forward gain is being filtered into irrelevance. Fix: After finding your ff values, incrementally raise ff_smooth_factor until you feel the nervous edge, then back off by 5.
Mistake 4: Copying Pro Pilot Settings Blind
That pro racer’s ff = 150 tune was developed on a 180g dry-weight rig with 2207 2700KV motors on 6S. Your 650g freestyle build with a GoPro will oscillate uncontrollably. Fix: Understand the physics — feed forward is amplified by high power-to-weight ratio. Heavier builds need more, not less.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
As we detailed in our Betaflight PID Tuning From Scratch guide, feed forward is the final layer of a complete tune — it can’t compensate for fundamental PID errors. If you’re still fighting propwash oscillations, revisit our Betaflight RPM Filtering Setup guide to ensure your noise floor is clean before pushing feed forward higher.
For pilots running aggressive rates, feed forward response is directly tied to how fast your stick moves. As we covered in Betaflight Rates Configuration, higher RC rate values produce steeper stick curves — which in turn generate more feed forward action per millimeter of stick deflection.
The feed forward settings above require a flight controller with a modern F7 or H7 processor to maintain low loop times under 4kHz. If you’re building a new rig, the SpeedyBee F405 V4 stack handles 4kHz PID loops with feed forward comfortably at a reasonable price point — and its onboard Bluetooth makes field tuning painless.