Hardware

Hardware is the single home for every setting that belongs to the physical stick or yoke.

Device here, aircraft under Tuning

Select the base, set its safe physical ceiling, calibrate axes, and assign device controls here. Set the way a particular aircraft feels under Tuning.

Select the device and validated backend

Choose the intended force-feedback device when more than one is connected. Known hardware selects its validated raw or operating-system path automatically; change the backend only while troubleshooting.

Figure 1. The Device tab identifies the selected base and the validated force-feedback path in use.

What has actually been validated

FFB-Bridge identifies the device and selects its validated input, force output, effect rendering, and safety policy automatically.

Hardware family	Current evidence and boundary
Microsoft SideWinder Force Feedback 2	The broadest field history: raw HID/PID by default with DirectInput fallback on Windows, evdev on Linux, and raw IOHID/PID on macOS.
Logitech G940 · Force 3D Pro · WingMan Force 3D	The G940 runs on its own decoded force protocol on Windows, Linux, and macOS (16-bit constant force, native spring, damping channel, and native centering), validated on all three, with the platform driver paths as automatic fallback. The Force 3D Pro and WingMan Force 3D use the platform driver paths; on Linux, sticks whose driver renders no periodic effects get rumble, buffets, and mechanical cues synthesised automatically into the constant-force output.
MOZA AB6 · AB9 · AY210	AB6 (346e:1002), AB9 (346e:1000), and AY210 (346e:1001) are separate supported device identities with model-specific capability policy. Managed configuration is supported across Windows, Linux, and macOS, and official physical Autopilot Follow is validated on all three bases.
Brunner FFB-G	Validated on Windows, Linux, and macOS with the supported platform-native force path.

Unlisted devices remain experimental

Unlisted joystick-class devices are an experimental opt-in with conservative 20% defaults. Wheels, gamepads, and single-axis devices are excluded; use FFB Probe to characterize unsupported hardware.

Default ceilings reflect evidence and device class: 100% for legacy consumer SideWinder/Logitech sticks, 35% for known high-force MOZA/Brunner bases, and 20% for eligible unlisted joysticks. Begin at the assigned limit and lower it whenever the mounted device or pilot requires less force.

Set physical limits before aircraft gains

The Effects tab defines what the hardware may physically produce. These safeguards remain active during normal flight and Flight Check.

Maximum physical strength is the hard ceiling for this device and rig.
Vibration & detail is an independent absolute ceiling for rumble, buffet, shudders, and transient cues.
Rendering policy is selected from validated device behavior; avoid compensating with a second configuration utility.
Axis and force-direction calibration correct the physical device once, independently of aircraft profiles.

Figure 2. The Effects tab keeps physical strength, validated rendering, and device-level limits together.

Vibration and detail has its own ceiling

The Vibration & detail slider runs from 0 to 100% of device command and does not change pitch or roll authority. Until you set it, it follows the lower axis ceiling; after you set it, the value is saved for that device. Use aircraft-profile effect gains in Tuning to balance individual cues, and use this Hardware ceiling to limit their combined physical output.

Figure 3. The MOZA control centre shows independent Pitch, Roll, and Vibration & detail ceilings for the selected base.

Assignments are explicit

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.

Figure 4. The Helicopter tab starts unassigned and opens the same guided setup pattern for all three controls.

Set up one beep-trim 4-way control

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.

Figure 5. 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 6. FTR releases the held point while pressed and establishes the current cyclic position when released.

Figure 7. 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.

Let Flight Check apply test values

Do not bounce between pages to prepare a hardware test. Flight Check applies the temporary value it needs and restores your previous state afterward. Open the Flight Check guide.