FFB-Bridge 1.3.1-beta.9
What’s new
- MOZA hardware control is gathered in one place.
Hardware → MOZA owns the base output envelope, health telemetry, and isolated damping, friction, inertia, and progressive-stop tests. Aircraft-specific values remain under Tuning → Aircraft control feel. AY210 and AB9 isolated mechanics have been verified on real Windows hardware.
- Force trim can use a separate Windows USB grip.
A Warthog or similar controller can supply FTR and its optional toggle while the force-feedback base remains the actuator. AP-follow roll direction is corrected, and elevator/aileron aerodynamic loading can be balanced independently.
- Flap and engine feel follow more of the real aircraft.
Actual flap travel drives movement, drag, and buffet, with a separate arrival bump. The default X-Plane C172 flap buffet is gentler. RPM, combustion, vibration, and reverse now aggregate every installed engine—MSFS engines 1–4 and X-Plane engines 0–7.
- Stall and overspeed cues can build progressively.
Valid AoA together with a plausible stall reference ramps stall buffet before the binary warning. Structural ice conservatively advances that envelope. A valid dynamic redline/Vne ramps overspeed buffet. Existing simulator warnings remain the fallback.
- Configuration effects use actual aircraft state where available.
Real gear and left/right spoiler deployment drive sustained drag and buffet. Measured wheel skid drives brake shudder, allowing ordinary non-skidding braking to remain smoother. MSFS native shaker intensity and surface condition are also used.
- X-Plane helicopters gain native blade-slap input.
The X-Plane 12 blade-slap ratio supplements the existing two-per-revolution model.
- MSFS Slew mode is a hard force-neutral state.
Constants, springs, textures, one-shots, and device-local condition metadata all drop to zero while Slew mode is active and recover when Slew mode ends.
- Optional telemetry cannot take down the core stream.
Each new MSFS value has an isolated definition, X-Plane zero-only unsupported signals retain their existing fallback behavior, and cached values clear when the aircraft changes.
