Skip to content

Chapter: Flair Crashes

Overview

Flair application crashes, hangs, and unexplained closures across both Flair Classic and Flair 7. Crash types range from specific reproducible triggers (opening Graph View with an invalid axis type, saving from the DMX popup) to intermittent crashes under time pressure (rapid speed warning dismissal). FBX-related crashes have their own dedicated issues in the CGI Motion chapter.

Most crash conditions are Flair Classic-specific. Flair 7 is generally more stable, and for several issues (including FBX import) switching to Flair 7 is the primary workaround.

Crash Recovery

After any Flair Classic crash: 1. Check "current job" — the last loaded job may be preserved in memory if Flair was writing to the current job buffer before the crash 2. Check the most recently saved .job file — if you saved to disk before the crash, that version is safe 3. If both are gone, the move data is not recoverable — save frequently, especially on location

Issue Index

Issue Status First Seen
Debug Assertion Dialog - Abort / Retry / Ignore FIELD GUIDANCE 2023-03-16
Graph View Crash — Axis Type 'Unused' RESOLVED 2023-03-18
Speed Warnings Crash — Move Lost From Current Job ONGOING 2023-04-26
FBX Import Crashes Flair Classic ONGOING 2026-02-12
DMX Popup Crash — Missing Driver Files RESOLVED 2020-12-15

FBX Crash Notes

FBX export crashes in Flair Classic (pre-Dec 2022) are documented separately: - CGI-fbx-crashes-after-export.md — export crash, fixed in Classic 7.2 (17 Dec 2022) - CRASH-fbx-import-crashes-classic.md — import crash, ongoing as of 2026

Official Documentation References

Document Notes
Flair Linux Setup v1.4 — whole document Linux installation / startup reference
Flair 7 Operator Manual - PDF p.1: startup and basic operation General startup and operator reference

See Also

  • CGI Motion — FBX export and import crash issues