Version changes through 1.1.0
FSS calls version 1.1.0 Service Update 1. Some news coverage calls it Service Pack 1; that is the same 2 November update, not a separate release. The current E-Jets page says Version 1.0 ended Early Access and is compatible with MSFS 2020 and 2024; the dated release article and #news post identify 1.1.0 as the later update. The 1.0.1 and 1.0.2 notices record earlier fixes: 1.0.1 addressed delayed loading, APU power at spawn, Navigraph requests, conflicting control bindings and recovery from overspeed protection. Version 1.0.2 addressed pitch/roll oscillation and autothrottle speed wandering; Service Update 1 repeats those fixes. Version 1.0.0 also added Hoppie CPDLC. FSS announced 1.1.0 in #news on 2 November and linked its update procedure. The SU1 article places Service Update 2 in a future phase; on 10 November, it still had no release notice or changelog. FSS describes the first native MSFS 2024 version as a target for before Christmas, subject to development and testing. Treat both items as plans, not released features. FSS E-Jets [1] · FSS News Hub [76] · Service Update 1 [2] · news coverage titled Service Pack 1 [77] · FSS #news, 1.0.0 [78] · FSS #news, 1.0.1 [79] · FSS #news, 1.0.2 [80] · FSS #news, 2 November 2026 [3].
Flight-management changes: Version 1.1.0 adds Vertical Direct-To and FIX INFO, and expands the existing step-climb logic. A Vertical Direct-To builds a new vertical path from a waypoint constraint. Step-climb entries use /FLXXXS and check predicted weight. FIX INFO plots radial or distance intersections on the MFD. Set the newly cleared altitude on the glareshield before VNAV follows a step climb. The roadmap still lists all three as in progress, though it says it covers only selected work items. The NAV page still says FIX INFO is not implemented. See the source-conflict section for details. In your installed build, check which MCDU pages and prompts appear. One 8 November support post reported that the VSD magenta path did not update after Vertical Direct-To, although the aircraft reportedly reached the waypoint altitude. The poster entered the constraint from FPL; FSS specifies ACT RTE. Because the post does not describe the documented ACT RTE procedure, it does not show whether that procedure failed. The thread had no reply or diagnosis. Community-support report, 8 November 2026 [70].
Other changes: EFB takeoff and landing distance calculations appear after generating a manifest; RAAS is available per livery and off by default; BeyondATC and SayIntentions provide PDC, CPDLC and ATIS through the MCDU when selected in EFB settings. The update also changes engine residual-heat modelling: above 120°C ITT, the start begins with dry motoring until the temperature falls below that threshold. The changelog also adds a barometric-setting alert at the transition altitude, improves autobrake and DES NOW behaviour, and fixes A/T disconnect audio, the inverted speed-knob event, HSI wind arrows, rudder steering snap-back, and Xbox controller input. It says DEL on a procedure altitude or speed clears that published limit; review the route carefully before using DEL. Check the linked update article for the complete changelog.
Before updating, read the linked FSS update procedure [81]. It includes clearing the E-Jets work folder; the #news post links it as a way to avoid WASM loading problems. After installation, let the first aircraft load finish so MSFS can compile the WASM module.
A 7 November community-support post described an E195 LR on MSFS 2024 that remained stuck loading after a clean 1.1.0 reinstall; the reported wait was about 15 minutes. The author mentioned Aerosoft One and the FSS Support tool, but the post does not establish whether every step in the current FSS update procedure was followed. No cause or fix was confirmed. This is one report, not evidence that every 1.1.0 installation is affected. If the same issue occurs, follow the current update procedure once if you have not already done so; if loading still fails, record the simulator, variant, installer and version and contact FSS support rather than repeating cleanup without a diagnosis. Community-support report, 7 November 2026 [82].