AIRLINE PACKS PERSONALISE THE CABIN WITHOUT REPLACING ITS LOGIC
The V3 Airline Pack system replaces and extends the earlier cabin-announcement arrangement. The developer guide identifies supported custom content such as boarding music, announcements, FAP recordings, EFB wallpaper and FAP screensaver images. Keep the pack's role distinct from the aircraft's physical equipment and performance profile. An airline-specific sound or background can be present while the loaded engine, wing or cabin configuration still needs its own check. Conversely, an unavailable announcement file does not prove that the underlying cabin event or door state failed. [81, Airline Packs: supported content and relationship to Virtual Purser]
The documented V3 installation uses an AirlinePacks folder inside a Community package, with the airline-code folder matched to the flight number or configured airline identity. The current guide describes a default fallback when a specific pack is not found. Verify the active identity and resulting content before concluding that a newly installed folder is in use. Keep the package intact during an update so its expected audio and image files remain together. The operational check is the event and content actually observed in the selected aircraft. [81, Current Airline Pack location, identity matching and fallback]
For a pack test, choose one known event and one identifiable piece of content. Establish whether the event occurred, whether the expected pack was selected and whether the appropriate audio/output channel was available. This separates matching, missing-file and presentation problems from the cabin sequence. Use the supported formats and filenames from the current developer guide when authoring content rather than inferring them from an unrelated legacy pack. A successful playback of boarding music does not independently validate every safety announcement or language/tag branch. [81, Audio/image content, events and pack customisation] [81, Current V3 cabin/interphone sound and event context]
Some cabin behaviours are controlled through EFB/livery preferences rather than through a sound file. Examples documented by Fenix include nighttime lighting, lavatory locking and the turnaround door policy. Select the behaviour deliberately and inspect the resulting cabin/FAP state. Keep the actual readiness indication as the completion check, even if the pack's audio makes the sequence sound familiar. Where a particular announcement is optional or absent from the active pack, distinguish that content choice from the flight crew's required coordination and observation. [81, VP Behaviour: lighting, lavatories, doors and cabin events] [70, Virtual Purser and airline-pack settings]
Retain the pack version and selected aircraft/livery in a reproducible cabin report. Test after a product update when event handling or content rules may have changed, retaining the V3 distinction between expediting cabin work and receiving its readiness result. This edition does not claim that every third-party pack has been audited. Evaluate each by its supported files, event coverage and observed result. A useful customisation improves recognition of the operation while leaving the actual aircraft-state checks clear. [81, Current V3 events and readiness expediting] [135, Official issue-reporting route]