Current release documentation FFB-Bridge 1.3.1 Found something stale? Tell us in the feedback form.

Helicopters

Version 1.3 treats the cyclic as a helicopter control system rather than a fixed-wing stick with a different profile name.

Start with a Rotorcraft profile

Create or select the aircraft profile, set its aircraft type to Rotorcraft, and choose Classic force trim when the helicopter uses a conventional trim-release system.

Select Rotorcraft once; the profile shows helicopter controls and hides fixed-wing settings that do not apply. Select Rotorcraft once; the profile shows helicopter controls and hides fixed-wing settings that do not apply.
Figure 1. Select Rotorcraft once; the profile shows helicopter controls and hides fixed-wing settings that do not apply.

Assign only the controls you want

Choose Set up… for the FTR button, optional force-trim on/off button, or beep-trim 4-way control. Each opens the same guided modal, waits while device input is prepared, then animates only while a press or direction can be captured. Nothing is assigned automatically, and simulator keybindings are never changed.

  • FTR releases the held point while pressed and establishes the current cyclic position when released.
  • Beep trim moves the held point slowly and continuously while an assigned direction is held.
  • Use one physical hat-shaped control for top, bottom, left, and right. FFB-Bridge listens to both input formats and saves either one POV hat or four buttons—whichever the device actually reports. The tested AY210 uses four buttons. Cancel or failed verification restores the previous assignment.
The Helicopter tab starts unassigned and opens the same guided setup pattern for all three controls. The Helicopter tab starts unassigned and opens the same guided setup pattern for all three controls.
Figure 2. The Helicopter tab starts unassigned and opens the same guided setup pattern for all three controls.
The guide explains POV versus buttons, pauses the current assignment, prepares input without a moving progress bar, then verifies all four directions before saving one input shape. The guide explains POV versus buttons, pauses the current assignment, prepares input without a moving progress bar, then verifies all four directions before saving one input shape.
Figure 3. The guide explains POV versus buttons, pauses the current assignment, prepares input without a moving progress bar, then verifies all four directions before saving one input shape.

Tune the control system, then the rotor cues

Establish cyclic damping and trim behavior first. Add rotor-state cues afterward so a vibration never hides a control-system problem.

  • Cyclic damping resists motion in proportion to movement, adding stability without dragging the stick back to an artificial fixed centre.
  • Hold FTR to move freely, release it to establish the new held position, or walk that position slowly with explicitly assigned beep trim.
  • ETL, VRS, two-per-revolution, retreating-blade stall, rotor rumble, and skid contact arrive as distinct cues you can tune or disable.

Validate the complete setup on the bench

The guided helicopter finale runs the full rotorcraft sequence on the bench. Individual steps isolate damping, force trim, beep trim, and every rotor cue using repeatable temporary settings.

The animated helicopter timeline names the current phase while the matching force runs. The animated helicopter timeline names the current phase while the matching force runs.
Figure 4. The animated helicopter timeline names the current phase while the matching force runs.
Keep guided tests out of a live flight

Do not run guided force tests during a live flight. Centre the control, secure the base, keep loose objects clear, and stay ready to disarm.

PreviousHardware NextFlight Check