Beginner’s CompanionRevision 3.1
FNX-FANTHE FLIGHT COMPANIONS
BEGINNER / REVISION 3.1

V3 BUILD NOTES - 26 OCTOBER 2026

Contents

These notes describe a dated V3 snapshot, recorded for this edition on 26 October 2026. On 22 October, Fenix announced hotfix 3.0.0.7454. Its release note records preservation of a manually entered route during arrival selection, a FAP camera view in MSFS 2024, and fixes for an MSFS 2020 exterior cabin-door issue and ACT-refuelling-panel flicker. The simulator platform matters in that list because some changes concern only the named platform. Use the version and date to identify what the note describes, then check the applicable release information for your installed build when investigating a result. [66, Official announcement, 22 October 2026; version 3.0.0.7454]

The developer known-issues post dated 24 October, edited 25 October, explains that Send to MCDU on mass and balance transfers live aircraft weights and trim rather than loadsheet values. Compare the entries actually accepted with the aircraft's loading and final loadsheet. That distinction can explain why a transferred value differs from a document open beside it. The same snapshot lists prediction-computation, manual-hold sequencing and managed-speed issues under investigation. Those entries record the developer's investigation at that date. When testing a related issue, record the installed build and a repeatable sequence so the observation can be compared with the appropriate information. [42]

Other items in that snapshot concern localizer/glideslope reception range, FAP interaction in MSFS 2020, and answering Cabin Ready through the cockpit intercom. The developer also identifies a supplied dynamic unreliable-speed table as A320-only. Check that a document applies to the aircraft being flown before using it across the family. Similar cockpit layouts do not establish the applicability of a table. Keep these dated notes alongside the enduring system explanations: the system description helps us understand the expected relationship, while the build record identifies reported behaviour at a particular point in development. Revisit the relevant note as the installed software changes. [42]

Back to contents