Boeing 777-300ER
Boeing 777-300ER: Artificial yoke feel motivates the configured powered-control response; the presence of fly-by-wire does not imply a passive Airbus-style inceptor.
Aircraft and simulator scope
- Boeing 777-300ER · MSFS 2020 · Variant starting point
- Boeing 777-300ER · MSFS 2024 · Variant starting point
- Boeing 777-300ER · X-Plane 11 · Variant starting point
- Boeing 777-300ER · X-Plane 12 · Variant starting point
PMDG 777-200LR and -200ER product documentation; -300/-300ER/freighter details are family inheritance. · Selected choice: Boeing 777-300ER. Documentary scope does not establish every variant, add-on revision or simulator binding.
The simulator model and controls
The 777 entered service in 1995 after development with input from major airline customers. Its broad cabin and two very large engines filled a space between the 767 and 747. The programme expanded through different fuselage lengths, range developments and engine choices.
This starting point selects Boeing 777-300ER. Its aircraft-level settings do not select a particular developer’s custom systems.
How this profile feels
Spring resistance builds with the selected airspeed response. Directed aerodynamic loading is omitted.
Pitch-trim relief is off. Autopilot following is enabled for supported control references.
Controls and trim
The 777 combines fly-by-wire with a conventional yoke, unlike the passive Airbus sidestick. PMDG describes C-star-U laws and artificial feel, with normal/direct behavior and custom trim logic. ER, LR, 300ER and freighter configurations retain different engines and product identities. FlightFactor's v2 X-Plane family is separately scoped from its older 777 package and from PMDG's implementation.
About the values
The gains are normalized profile settings. They describe the chosen effect balance; hand force depends on the device and its output limits. IAS references are tuning values rather than operating limits. Physical acceptance of this revision remains pending.
Documentary review and sources
These decisions describe the documentary basis and remaining gaps for this revision. Aircraft documentation and a starting setting describe different kinds of evidence.
Aircraft and variant
InheritedThis starting point selects Boeing 777-300ER. Its aircraft-level settings do not select a particular developer’s custom systems.
Flight controls
InheritedThe 777 combines fly-by-wire with a conventional yoke, unlike the passive Airbus sidestick. PMDG describes C-star-U laws and artificial feel, with normal/direct behavior and custom trim logic. ER, LR, 300ER and freighter configurations retain different engines and product identities. FlightFactor's v2 X-Plane family is separately scoped from its older 777 package and from PMDG's implementation.
Trim
InheritedAircraft trim-rate and law behavior are documented, but a disabled profile trim response omits their hardware effect rather than reproducing them. Pitch relief is off, with stored authority 0; roll authority is 0.
Autopilot and stability
InheritedFollowing is on at 1 authority when a supported, valid autopilot control reference is available.
Equipment
InheritedGear, flap and ground cues follow the selected settings and available simulator-reported states.
Speeds and limits
Not yet reviewedThe indicated-speed references set the profile response scale; they are separate from aircraft operating limits.
Simulator integration
Not yet reviewedThe profile targets msfs2020, msfs2024, xplane11, xplane12. Add-on-specific controls use only the supported references configured by this profile.
Force-feedback settings
Not yet reviewedThe settings define the profile’s effect balance. Device output limits affect physical hand force.
Starting settings and their rationale
These configured values are starting estimates. The explanations describe what each setting controls; physical validation appears separately below.
| Setting | Starting value | What it controls and why |
|---|---|---|
| Spring strength | Starting value0.2 | What it controls and whyArtificial yoke feel motivates the configured powered-control response; the presence of fly-by-wire does not imply a passive Airbus-style inceptor. The baseline spring is 0.2. Low-speed spring blending is off. |
| Master force gain | Starting value0.85 | What it controls and whyScales overall profile strength while preserving effect balance, subject to device and output limits. |
| Profile force gain | Starting value0 | What it controls and whyThe 0 gain omits sustained directed airspeed loading. Spring resistance remains independent. |
| Force tuning speed/reference | Starting value275.0 kt | What it controls and whySets the IAS reference for aerodynamic loading. It is an estimate, not published cruise TAS or a flight limit. |
| Spring response reference speed | Starting value122 kt | What it controls and whySets the IAS where the low-speed blend reaches baseline strength; high-speed stiffening also uses it. |
| Aileron force scale | Starting value0.65 | What it controls and whyRoll and pitch aerodynamic scales are 0.65 and 0.65, respectively. These stored weights do not create directed aerodynamic loading while that term is inactive. No custom spring-travel curve is enabled. |
| Elevator force scale | Starting value0.65 | What it controls and whyScales pitch aerodynamic loading; pitch spring travel and trim responses are separate settings. |
| Trim feel | Starting valueDisabled | What it controls and whyRetained for compatibility and group membership. Trim relief, rather than this flag, controls centre movement. |
| Trim relief | Starting valueDisabled | What it controls and whyAllows trim relief with supported control law and valid telemetry. Axis authorities set its amount. |
| Autopilot follow | Starting valueEnabled | What it controls and whyFollowing is on at 1 authority when a supported, valid autopilot control reference is available. |
| Autopilot neutral hold | Starting valueDisabled | What it controls and whyPermits centering hold during a supported AP state, separate from following a moving target. |
| Output force limit | Starting value0.55 | What it controls and whyCaps directed-force output. Native spring effects and device limits remain separate. |
All 46 starting settings and their rationale
The settings define the profile’s effect balance. Device output limits affect physical hand force.
| Setting | Starting value | What it controls and why |
|---|---|---|
| Spring strength | Starting value0.2 | What it controls and whyArtificial yoke feel motivates the configured powered-control response; the presence of fly-by-wire does not imply a passive Airbus-style inceptor. The baseline spring is 0.2. Low-speed spring blending is off. |
| Spring deadband | Starting value0.0 | What it controls and whySets travel around the centre before the baseline spring resists. Smaller values engage it sooner. |
| Starting centering force | Starting value0.04 | What it controls and whyAdds smoothly ramped resistance outside the centre deadband. Zero removes this preload. |
| Center Starting Force Transition | Starting value0.05 | What it controls and whySets the travel used to ramp in centre preload. Wider intervals make its onset more gradual. |
| Profile force gain | Starting value0 | What it controls and whyThe 0 gain omits sustained directed airspeed loading. Spring resistance remains independent. |
| Master force gain | Starting value0.85 | What it controls and whyScales overall profile strength while preserving effect balance, subject to device and output limits. |
| QBlend Enabled | Starting valueDisabled | What it controls and whyAllows baseline spring strength to rise with indicated airspeed where the control law permits it. |
| QSpring Minimum Factor | Starting value0.55 | What it controls and whySets low-speed spring strength as a fraction of baseline when blending is enabled. One keeps full strength. |
| QSpring Start Knots | Starting value20 kt | What it controls and whySets the IAS where the low-speed spring blend starts rising. This is a feel threshold, not a flight limit. |
| Spring response reference speed | Starting value122 kt | What it controls and whySets the IAS where the low-speed blend reaches baseline strength; high-speed stiffening also uses it. |
| Force tuning speed/reference | Starting value275.0 kt | What it controls and whySets the IAS reference for aerodynamic loading. It is an estimate, not published cruise TAS or a flight limit. |
| Airspeed spring stiffening gain | Starting value1.0 | What it controls and whyThe high-speed spring-stiffening gain is 1. It strengthens the permitted spring response above 122 KIAS, with the squared-speed ratio capped at 7.8. |
| Airspeed spring stiffening limit | Starting value7.8 | What it controls and whyLimits the squared airspeed ratio used for high-speed spring stiffening; it is not a device-force cap. |
| Aileron force scale | Starting value0.65 | What it controls and whyRoll and pitch aerodynamic scales are 0.65 and 0.65, respectively. These stored weights do not create directed aerodynamic loading while that term is inactive. No custom spring-travel curve is enabled. |
| Elevator force scale | Starting value0.65 | What it controls and whyScales pitch aerodynamic loading; pitch spring travel and trim responses are separate settings. |
| Output force limit | Starting value0.55 | What it controls and whyCaps directed-force output. Native spring effects and device limits remain separate. |
| Trim feel | Starting valueDisabled | What it controls and whyRetained for compatibility and group membership. Trim relief, rather than this flag, controls centre movement. |
| Trim relief | Starting valueDisabled | What it controls and whyAllows trim relief with supported control law and valid telemetry. Axis authorities set its amount. |
| Elevator Authority | Starting value0 | What it controls and whyAircraft trim-rate and law behavior are documented, but a disabled profile trim response omits their hardware effect rather than reproducing them. Pitch relief is off, with stored authority 0; roll authority is 0. |
| Aileron Authority | Starting value0 | What it controls and whyScales supported roll-trim relief and permitted centre movement. Zero removes roll response. |
| Force Trim Enabled | Starting valueDisabled | What it controls and whyEnables local force trim, separate from aircraft-owned trim and add-on integration qualification. |
| GLoad Enabled | Starting valueDisabled | What it controls and whyAllows load-factor changes to modify permitted spring laws. Passive fly-by-wire feel can suppress it. |
| Rate Damping Enabled | Starting valueDisabled | What it controls and whyEnables rate damping with the configured coefficients and control law. |
| Autopilot follow | Starting valueEnabled | What it controls and whyFollowing is on at 1 authority when a supported, valid autopilot control reference is available. |
| Autopilot follow authority | Starting value1.0 | What it controls and whySets admitted AP-follow gain, not a percentage of travel. Runtime ownership and input limits still apply. |
| Autopilot neutral hold | Starting valueDisabled | What it controls and whyPermits centering hold during a supported AP state, separate from following a moving target. |
| Autopilot neutral hold strength | Starting value0.6 | What it controls and whySets admitted AP neutral-hold strength; inactive while neutral hold is disabled. |
| Enabled | Starting valueEnabled | What it controls and whyEnables aerodynamic cues; each still needs nonzero strength and its simulator conditions. |
| Gain | Starting value0.3 | What it controls and whySets stall-buffet strength. Zero removes the cue without changing simulator stalls or warnings. |
| Gain | Starting value0.22 | What it controls and whySets high-Mach buffet strength; onset and full-strength thresholds are separate. |
| Gain | Starting value0.14 | What it controls and whySets flap buffet at the configured position and speed gates. Flap movement texture is separate. |
| Maximum flap index | Starting value6 | What it controls and whySets the final flap index for detent normalization. UP plus three detents uses maximum index3. |
| Minimum flap index | Starting value2 | What it controls and whySets the first flap detent that admits buffet; this is a handle index, not degrees. |
| Gain | Starting value0.1 | What it controls and whySets gear aerodynamic buffet; movement and ground-contact cues are separate. |
| Shaker Enabled | Starting valueEnabled | What it controls and whyPermits shaker at supported warning conditions; the switch does not establish aircraft equipment. |
| Stick shaker amplitude | Starting value0.9 | What it controls and whySets triggered shaker strength; inactive while the shaker feature is disabled. |
| Enabled | Starting valueEnabled | What it controls and whyEnables ground effects; each still needs its own strength and contact or motion telemetry. |
| Gain | Starting value0.4 | What it controls and whySets rolling texture strength, modified by speed, surface and undercarriage configuration. |
| Gain | Starting value0.32 | What it controls and whySets gear-bump texture during ground motion, separate from touchdown impact. |
| Gain | Starting value0.9 | What it controls and whySets landing-impact strength; landing telemetry and response shape determine the pulse. |
| Gain | Starting value0.5 | What it controls and whySets reverse-thrust vibration with valid reverser and engine conditions. Zero removes the cue. |
| Enabled | Starting valueEnabled | What it controls and whyEnables engine cues with nonzero settings and valid running-engine telemetry. |
| Gain | Starting value0.06 | What it controls and whySets estimated engine vibration using configured telemetry and response, not measured cockpit vibration. |
| Enabled | Starting valueEnabled | What it controls and whyEnables accessory cues with configured strengths and observed accessory movement. |
| Gain | Starting value0.12 | What it controls and whySets texture from observed flap movement; a command without movement does not establish the cue. |
| Gain | Starting value0.12 | What it controls and whySets texture from observed gear movement, separate from aerodynamic and touchdown effects. |
Limits and open questions
- The PMDG LR page identifies a custom autopilot and C-star-U fly-by-wire implementation; the ER page is a separate scope.
- For Boeing 777-300ER, the cited feature is inherited from the explicitly scoped family/implementation evidence; this variant was not separately established by that source.
- Normal/direct fly-by-wire laws and artificial-feel behavior are advertised; control-law realism is not measured physical force.
- Trim-rate/logic behavior is advertised. Current preset trim response is disabled, so public evidence must not imply that it reproduces these features.
- A custom autopilot and fly-by-wire logic are described; generic following has no qualified external servo contract.
- The ER source distinguishes three engine variants; common family force settings do not recreate those engine-specific details.
- Product descriptions do not derive the selected indicated-speed force reference or a complete 777 load schedule.
- Custom C-star-U and autopilot logic require add-on-specific telemetry/ownership checks.
- The source gives no numerical force calibration. Current aerodynamic blending and force gain are disabled, unlike older variable-feel descriptions.
Physical validation
No physical force validation is recorded in this public catalogue for this revision. Documentary review and software checks do not establish how a particular device feels.