Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Aircraft and configuration
SwissMilSim represents the Hunter Mk.58 with powered pitch and roll controls and automatic stabiliser gearing. The MSFS 2024 product offers historical liveries and external tanks.
Hawker Hunter Mk.58
SwissMilSim · Read more ↗Meet Hawker Hunter Mk.58
SwissMilSim represents the Hunter Mk.58 with powered pitch and roll controls and automatic stabiliser gearing. The MSFS 2024 product offers historical liveries and external tanks.
History & design
From RAF fighter to overseas ground attack
The Hunter entered RAF service in July 1954 with fully powered flying controls. As the Lightning took over the interceptor role from 1960, the Hunter continued in ground attack. A 1958 competition selected a modified F6 to replace the Venom in the Middle East; the first FGA9 flew in July 1959.
That adaptation gave the airframe a second operational chapter, including overseas service until the last Hunter ground-attack squadron, No. 8, disbanded in 1971. The RAF Museum’s FGA9 history establishes this British development path. The Swiss Mk.58 represented by SwissMilSim is a different national variant and should be identified from its own manual and equipment list.
Royal Air Force Museum · Hawker Hunter FGA9 ↗Systems & details
Controls and equipment
The manual marks certain servo-release and failure functions as unimplemented.
Simulated equipment
The native MSFS 2024 product includes external tanks and historical liveries. Some weapon and parachute functions are unimplemented.
In your simulator
No released simulator product is listed for this aircraft in the developers reviewed. Announced products are excluded.
Manuals & resources
Find your next read
Choose a topic for a short introduction and a link to the original source. Simulator references identify the developer and edition they cover.
Simulator documentation
Controls and equipmentHawker Hunter Mk.58
The manual marks certain servo-release and failure functions as unimplemented.
Hunter flight manual · pages 22 and 49–54
SwissMilSim · Read the source ↗Simulated equipmentHawker Hunter Mk.58
The native MSFS 2024 product includes external tanks and historical liveries. Some weapon and parachute functions are unimplemented.
Hunter Mk.58 product configuration
SwissMilSim · Read the source ↗Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Simulator documentation
Hawker Hunter Mk.58 — simulator documentationSwissMilSim · Hunter flight manual · pages 22 and 49–54 Hawker Hunter Mk.58 — simulator documentationSwissMilSim · Hunter Mk.58 product configurationAircraft background
Hawker Hunter FGA9Royal Air Force Museum · The Hunter entered RAF service in July 1954. The later FGA9 was developed from the F6 for ground attack, with the first example flying in July 1959.Built-in force-feedback profiles
Read the documentary basis, editable starting settings and remaining questions for the aircraft you fly. Each explanation refers to the exact profile revision shown.
Catalogue programme-20261011-v3 · 1 profile choice
SwissMilSim Hawker Hunter Mk.58
SwissMilSim · Free and Pro · Revision 2 · Inherited starting point
MSFS 2024
The Swiss Hunter Mk.58 with powered pitch and roll controls.
SwissMilSim Hawker Hunter Mk.58
The Swiss Hunter Mk.58 with powered pitch and roll controls.
Aircraft and simulator scope
- SwissMilSim Hawker Hunter Mk.58 · SwissMilSim · MSFS 2024 · Add-on starting point
The simulator model and controls
SwissMilSim Hawker Hunter Mk.58 is the selected SwissMilSim configuration.
How this profile feels
Spring resistance builds with the selected airspeed response. A separate aerodynamic term adds speed-dependent control load.
Pitch-trim relief is off. Autopilot following is off.
Aircraft and configuration
SwissMilSim represents the Hunter Mk.58 with powered pitch and roll controls and automatic stabiliser gearing. The MSFS 2024 product offers historical liveries and external tanks.
Controls and equipment
The manual marks certain servo-release and failure functions as unimplemented.
About the values
Strengths are normalized hardware-feel settings. They set the effect balance; hand force depends on the device and its limits. The IAS reference is a tuning value.
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
InheritedSwissMilSim Hawker Hunter Mk.58 is the selected SwissMilSim configuration.
Flight controls
InheritedThe Swiss Hunter Mk.58 with powered pitch and roll controls.
Trim
InheritedThe profile uses the trim behaviour configured below. Pitch relief is off, with stored authority 0; roll authority is 0.
Autopilot and stability
InheritedAutopilot following is off; the configured spring and load retain the hardware feel.
Equipment
InheritedSwissMilSim represents the Hunter Mk.58 with powered pitch and roll controls and automatic stabiliser gearing. The MSFS 2024 product offers historical liveries and external tanks.
Speeds and limits
InheritedThe indicated-speed references set the profile response scale; they are separate from aircraft operating limits.
Simulator integration
InheritedThe profile targets msfs2024. Add-on-specific controls use only the supported references configured by this profile.
Force-feedback settings
InheritedThe 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.74 | What it controls and whyFlight controls: Powered pitch and roll. The baseline spring is 0.74. 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.25 | What it controls and whyThe aerodynamic-load gain is 0.25 with an indicated-speed reference of 250 KIAS. The hydraulic-load factor of 0.35 scales that modeled term; it is a selected artificial-feel approximation. |
| Force tuning speed/reference | Starting value250 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 value65 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.72 | What it controls and whyRoll and pitch aerodynamic scales are 0.72 and 1, respectively. They set the aerodynamic axis balance. No custom spring-travel curve is enabled. |
| Elevator force scale | Starting value1.0 | 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 valueDisabled | What it controls and whyAutopilot following is off; the configured spring and load retain the hardware feel. |
| 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 44 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.74 | What it controls and whyFlight controls: Powered pitch and roll. The baseline spring is 0.74. Low-speed spring blending is off. |
| Spring deadband | Starting value0.04 | What it controls and whySets travel around the centre before the baseline spring resists. Smaller values engage it sooner. |
| Profile force gain | Starting value0.25 | What it controls and whyThe aerodynamic-load gain is 0.25 with an indicated-speed reference of 250 KIAS. The hydraulic-load factor of 0.35 scales that modeled term; it is a selected artificial-feel approximation. |
| 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 value8 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 value65 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 value250 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 value0.15 | What it controls and whyThe high-speed spring-stiffening gain is 0.15. It strengthens the permitted spring response above 65 KIAS, with the squared-speed ratio capped at 5. |
| Airspeed spring stiffening limit | Starting value5 | 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.72 | What it controls and whyRoll and pitch aerodynamic scales are 0.72 and 1, respectively. They set the aerodynamic axis balance. No custom spring-travel curve is enabled. |
| Elevator force scale | Starting value1.0 | 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 whyThe profile uses the trim behaviour configured below. 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 valueEnabled | 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 valueEnabled | What it controls and whyEnables rate damping with the configured coefficients and control law. |
| Autopilot follow | Starting valueDisabled | What it controls and whyAutopilot following is off; the configured spring and load retain the hardware feel. |
| Autopilot follow authority | Starting value0.1 | 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.35 | What it controls and whySets stall-buffet strength. Zero removes the cue without changing simulator stalls or warnings. |
| Gain | Starting value0 | What it controls and whySets high-Mach buffet strength; onset and full-strength thresholds are separate. |
| Gain | Starting value0 | What it controls and whySets flap buffet at the configured position and speed gates. Flap movement texture is separate. |
| Maximum flap index | Starting value3 | 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 | What it controls and whySets gear aerodynamic buffet; movement and ground-contact cues are separate. |
| Shaker Enabled | Starting valueDisabled | What it controls and whyPermits shaker at supported warning conditions; the switch does not establish aircraft equipment. |
| Stick shaker amplitude | Starting value0.5 | 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.25 | What it controls and whySets gear-bump texture during ground motion, separate from touchdown impact. |
| Gain | Starting value0.65 | What it controls and whySets landing-impact strength; landing telemetry and response shape determine the pulse. |
| Gain | Starting value0 | 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.12 | 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.025 | What it controls and whySets texture from observed gear movement, separate from aerodynamic and touchdown effects. |
Limits and open questions
- Hydraulically assisted pitch and roll. Transonic automatic tail-incidence system is not a linear hardware-neutral law.
- Electric stabilizer incidence and roll/rudder trim documented; no calibrated boosted-stick-neutral contract. Both paths disabled.
- No calibrated autopilot servo or inceptor-demand output established. AP follow and neutral hold are disabled.
- 250 KIAS is an estimated tuning reference, not a certified operating limit or cruise TAS.
- Native read-only aircraft telemetry only. No custom interface names, units or freshness contract invented; switches and animated controls are not servo demands.
- Spring 0.74, lateral scale 0.7, pitch/roll relief 0/0; editable estimates. No measured hand-force calibration, unsupported failure loads, surface-follow or body-rate torque.
- Installed-aircraft and physical checks are deferred. If telemetry omits the developer or configuration, select this profile and save it as the aircraft default.
- Only actual accessory-position changes drive movement textures. No release or installed-product acceptance is inferred.
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.
Discuss this aircraft (0)
Questions, observations and useful sources from the community.
No published discussions yet. Bring a question or share a useful source.
Open aircraft discussions →Content expanded · What’s new
Something missing or a source that needs attention?
Suggest a correction ↗