Synaptic Simulations has released v1.0.4 for its Airbus A220 for Microsoft Flight Simulator 2020 and 2024, focusing on improving performance and addressing a wide range of issues.
The update includes performance improvements to the ND and EICAS, alongside optimisations to the cabin that reduce draw calls, mesh vertices, and model nodes. Display textures have also been reduced in size by around 40 per cent.
Several systems and FMS issues have been fixed, including incorrect engine start values, APU start problems, navigation and flight plan issues, incorrect map displays, altitude constraint errors, and multiple FMS crashes. The EFB has also been optimised, with improvements to the Loadsheet page and chart aircraft-position overlay.
The full changelog can be found below.

You can download the update from the MSFS Marketplace now.
Synaptic Simulations A220 V1.0.4 Changelog
Systems
- Fixed – General pass over the ND and EICAS to make improvements to performance
- Fixed – Slightly adjust FMS cross-track gains when en route and on approach 1
- Fixed – Starting engines with throttles set to max causes crazy N1/N2/EGT values
- Fixed – APU start sequence broken when door opens before start request is commanded
- Fixed – Ailerons droop the wrong way in windy conditions
- Fixed – CI legs with no course change draw a loop on the map
- Fixed – CI legs find intercepts on the other side of the world
- Fixed – VA legs incorrectly treated as vectored when computing discontinuities
- Fixed – VM legs incorrectly treated as unvectored when computing discontinuities
- Fixed – IF legs not replaced with TF legs when clearing discontinuities 2
- Fixed – Top-of-descent marker pinned to aircraft’s present position
- Fixed – Turn arcs and intercept arrows are not always drawn correctly on the map
- Fixed – PFD displaying date one day ahead
- Fixed – PFD vertical and lateral deviation preview pointers using wrong icon for FMS source
- Fixed – Map OVLY task menu should time out after 2 seconds
- Fixed – Altitudes swapped when entering between altitude constraints into FMS
- Fixed – Missing runways in custom sceneries that would use “Macadam” or “Undefined” as surface types
- Fixed – FLAPS HANDLE INDEX variable not set to current detent 3
- Fixed – AUTOPILOT ALTITUDE LOCK VAR variable not set to current preselector altitude
- Fixed – Checklist RESET ALL function should only be selectable from index pages
- Fixed – Checklist INLET_OFF variable state flipped
- Fixed – VHF frequencies rounding down when set externally or when switching channel spacing
- Fixed – OFF indication missing on avionics cooling inlet switch
- Fixed – Incorrect relative altitude shown for TCAS traffic
- Fixed – Procedure identifiers on FMS PLAN INIT page not cleared when corresponding segment is deleted
- Fixed – Several incorrect indications on the AIRCRAFT information dialog
- Fixed – FMS crashes on PERF ARR, ROUTE POS REPORT, and ROUTE FLT LOG pages
- Fixed – Unable to select visual approaches from the FMS ARRIVALS dialog
- Fixed – Sometimes unable to select approaches from the FMS ARRIVALS dialog with native navdata
Art
Fixed – Reduced display texture size by roughly 40% by removing wasted space 4
Fixed – Reduced cabin draw calls, mesh vertices, and model node count for improved performance
EFB
Fixed – Loadsheet page negatively impacts performance
Fixed – Charts occasionally missing aircraft position overlay
Fixed – Removed “attach/remove covers” option from ground equipment page in MSFS 2020
Flight Model
Fixed – Doors are openable in flight
Footnotes
This should help reduce the cross-track deviation observed when flying along the flight plan route; a more comprehensive review of these gains is planned for a future update which will also include localizer capture
This manifested itself as persistent discontinuities in the flight plan on the map, despite the FMS ROUTE page showing no discontinuities; guidance remained unaffected in these cases
This caused compatibility issues with third-party software such as Newsky and A Pilot’s Life V2, and may have been responsible for incorrectly simulated flap damage with the simulator’s default damage model
This is expected to bring a sizeable improvement to performance, as less VRAM is used by the main displays and less time is taken on the graphics queue






