Best Fenix A320 settings for MSFS 2024, covering assists, throttle detents, controls, graphics, FPS and fixes for common conflicts.
For the Fenix A320 in Microsoft Flight Simulator 2024, use the Modern flight model, turn off piloting assists, create a dedicated control profile, and calibrate every throttle detent in the Fenix EFB. Keep aircraft options at default initially, then tune traffic, Terrain LOD, clouds and anti-aliasing to your actual CPU/GPU bottleneck.
These recommendations apply to the PC version. The Fenix A320 depends on its desktop application and is not available for the Xbox Series X|S or PlayStation 5 versions of MSFS 2024.
Recommended Fenix A320 settings at a glance
The safest baseline is a clean, assistance-free simulator profile with aircraft loading and calibration handled through the Fenix EFB.
| Setting area | Recommended baseline | Reason |
|---|---|---|
| Flight model | Modern | The Fenix flight-control model is designed around the modern simulator flight model. |
| Piloting assists | Off | Auto-rudder, assisted controls and AI piloting can interfere with Airbus protections and control inputs. |
| Control profile | Dedicated Fenix profile | Prevents duplicate axes and unwanted general-aviation bindings. |
| Throttle | Calibrate in the Fenix EFB | Required for reliable IDLE, CL, FLX/MCT and TOGA recognition. |
| Fuel and payload | Load through the Fenix EFB | Avoids conflicts with the simulator's fuel, payload and unlimited-fuel functions. |
| Aircraft failures | Off while configuring | Establish a working baseline before enabling random or scheduled failures. |
| Anti-aliasing | TAA or DLAA for clarity | Keeps PFD, ND and MCDU text sharper; use DLSS Quality if GPU performance is the priority. |
| Fenix display options | Default initially | Changing the renderer or display quality can move load between the CPU and GPU rather than simply reducing it. |
Which MSFS 2024 assistance settings should be disabled?
Disable any assistance that moves a flight control, changes engine operation or flies the aircraft on your behalf. The Fenix supplies its own Airbus control laws, autothrust logic and aircraft systems.
- Turn off: AI piloting, assisted yoke or control inputs, auto-rudder, assisted take-off, assisted landing, automatic trim and automatic engine management.
- Turn off unlimited fuel: set the required fuel in the Fenix EFB instead.
- Optional: checklist highlighting, taxi guidance and ATC assistance can remain enabled because they do not normally alter the flight model.
A mistake we see constantly is selecting an easier global assistance preset after configuring the aircraft. That can silently reactivate auto-rudder or other handling assists, so recheck the individual assistance options afterwards.
How should you calibrate Fenix A320 controls and throttle detents?
Use a separate MSFS control profile and complete the throttle calibration inside the Fenix EFB after assigning the axes.
- Create a Fenix-only profile: duplicate your existing controller profile, rename it clearly and remove bindings the Airbus does not need.
- Assign each axis once: bind aileron, elevator, rudder and each throttle lever to one appropriate axis. Remove duplicate assignments from gamepads, yokes and other connected devices.
- Choose one reverser method: use reverse travel on the throttle axis or a button-based reverser arrangement, not both at once.
- Calibrate every detent: follow the Fenix EFB prompts for reverse if used, IDLE, CL, FLX/MCT and TOGA. Give physical detents enough tolerance to prevent the indicated lever position flickering between ranges.
- Test in the cockpit: move the hardware slowly and confirm both virtual thrust levers enter the same detent together.
Start with a near-linear response and only add enough dead zone to remove actual jitter. If you alter axis sensitivity after calibration, calibrate the Fenix detents again. Our guide to Airbus control sensitivity and throttle setup explains the axis choices and detent process in more detail.
Which Fenix EFB options actually matter?
Throttle calibration, fuel loading and flight-plan integration matter; most other EFB choices are operational preferences rather than required performance settings.
- Fuel and payload: configure these through the Fenix EFB instead of changing them independently in the MSFS weight-and-balance panel.
- Failures: leave them disabled until the aircraft starts, displays and flies correctly. Enable them later if you specifically want failure practice.
- Aircraft state: cold and dark, turnaround and ready states change how much setup is required, not the aircraft's flight quality.
- Display or renderer option: if your installed Fenix build provides one, begin with its default. Change one option at a time and reload the aircraft if the application requests it.
Do not assume a route entered on the MSFS world map has populated the Fenix MCDU. For dispatch integration, use one consistent route source and follow our Fenix SimBrief import procedure rather than mixing independently generated plans.
Which graphics settings improve Fenix A320 FPS?
Change settings according to the limiting component shown by the simulator's FPS overlay; lowering every graphics option rarely fixes a CPU-limited Fenix flight.
| Observed limit | Reduce first | Keep if possible |
|---|---|---|
MainThread or CPU | Terrain Level of Detail, airport traffic, ground aircraft, road vehicles and other traffic density | Native resolution and cockpit texture clarity |
| GPU | Render scaling, clouds, reflections, ambient occlusion and shadow quality | Terrain LOD unless the CPU is also limiting |
| VRAM | Texture resolution and other high-resolution scenery options | Cockpit readability at the highest stable setting |
At native resolution, TAA is a dependable clarity baseline. DLAA is sharper when available but costs GPU performance; DLSS Quality can recover performance, although glass-cockpit text may look softer, especially at lower output resolutions. Frame generation can smooth presentation when the base frame rate is already stable, but it does not remove a MainThread bottleneck.
Do not rely on the simulator's Glass Cockpit Refresh Rate as the main Fenix fix. Custom Fenix avionics do not always follow that global option in the same way as default aircraft. For a bottleneck-by-bottleneck checklist, use our Fenix A320 performance and FPS settings.
Why do the throttle detents or cockpit displays still misbehave?
Persistent control or display problems usually indicate conflicting bindings, an incorrect calibration or a Fenix application problem rather than the need for lower graphics settings.
- Throttles miss CL or FLX/MCT: remove duplicate throttle bindings, widen the detent tolerance slightly and recalibrate after changing sensitivity.
- The aircraft fights your inputs: recheck AI piloting, auto-rudder and assisted-control options, including any settings re-enabled by a global preset.
- One lever moves both engines: verify that separate hardware levers use separate throttle axes and that no combined axis remains assigned.
- Displays are black or frozen: confirm the Fenix desktop application is running and that the aircraft was installed specifically for MSFS 2024. Restarting only the flight may not restart the external application.
- The route differs from the EFB: clear the MCDU route and import one plan consistently instead of combining world-map and dispatch data.
If calibration and assistance settings are correct but the aircraft still fails to initialise, follow our Fenix startup, display and add-on conflict checks.