V3-ONLY OPERATING INSTRUCTIONS AND COMMUNITY EVIDENCE
Revision 3.1 uses Fenix V3 for its operating instructions, settings and troubleshooting. Historical accounts explain earlier product development, while older software recipes are excluded from the current workflow. For navigation data, use the V3 A/C STATUS and EFB connection process described in the programming chapters. The selected database must be validated and its activation conditions satisfied before programming continues. [107, V3 update/import/activation sections]
Community discussion is useful for locating a problem and defining a test. A usable report identifies aircraft, simulator platform, build, configuration, symptoms and enough conditions to distinguish the observation from a guess. A report can establish that a user saw a behaviour; it does not by itself establish the cause, a universal operating limit or an approved remedy. The Pro discussion retains only V3-relevant community evidence and checks technical conclusions against the primary sources. [86, Failures guide; diagnosis and configured failures]
Practical verification follows a narrow sequence: preserve the observed state, record the inputs and result, check known configuration and source conditions, and change one relevant variable at a time. If a vendor issue remains plausible, retain the evidence needed for a support report. Resetting everything before recording the state can remove the information needed to understand the original discrepancy. [21, Use of automation and systematic aircraft-state assessment]