FBX Export — "Invalid Job" Error (Roll Mode Mismatch)¶
CGI Motion Resolved All rigs BOTH
Summary¶
When attempting to export a move as FBX, Flair reports "Invalid Job" and refuses to export. The most common cause is a roll mode mismatch: the move was programmed in one roll mode (e.g., Roll Level), but Flair's current session roll mode has since changed — often because returning the rig to Home resets the roll settings to a default.
Symptoms¶
- Clicking Export in the CGI Export dialog produces an "Invalid Job" error
- Only affects some jobs in a batch (e.g., 2 of 9 export fine but 2 fail)
- No other obvious reason — move data appears intact and runs correctly
Root Cause¶
FBX export in Flair validates that the move's programmed roll mode matches the active session roll mode at export time. When you send the rig to Home or switch tasks between moves, Flair can silently reset the roll mode. On returning to the job, the stored move data says "Roll Level" but Flair's current session says "Roll Relative" (or vice versa), so validation fails.
"I would often find myself finishing a job, then going to home — this automatically resets the roll settings to roll moves. When I export, I get a message that the job is invalid, then remember to switch back to roll level (or whatever the job was programmed in) and export again." — Radu Stefan Fulga
Resolution¶
Before exporting:
- Open the move in Flair.
- Check which roll mode the move was programmed in. In Flair this is visible in the move header / roll-mode controls; for target-tracking moves also check the relevant Target Tracking / Job Type controls.
- Ensure the current session roll mode matches the move's roll mode exactly before opening CGI Export / Move Export.
- Retry the FBX export.
Common mismatches
- Move programmed in Roll Level → session currently set to Roll Relative: switch back to Roll Level
- Move programmed in Roll Up → session currently set to Roll Level: switch to Roll Up, then use 3-node FBX export
Preventive Habit¶
Before any CGI export session with multiple moves:
- Note the roll mode for each move before you start (check move header or confirm with the operator who programmed it).
- Set the session roll mode to match in the move header / roll controls before opening CGI Export / Move Export.
- Do not use Home between exports unless you consciously reset the roll mode afterwards.
WhatsApp Excerpts¶
"You guys know any cheats when the job doesn't want to be cgi exported? It says invalid job on 2 moves out of 9." — Oscar Molano
"I would often find myself finishing a job, then going to home, this automatically resets the roll settings to roll moves. When I export, I get a message that the job is invalid, then remember to switch back to roll level (or whatever the job was programmed in) and export again." — Radu Stefan Fulga
Related Issues¶
- See also: FBX Export — 1-Node vs 2-Node vs 3-Node Explained — Which FBX node type to use for each roll mode
- See also: FBX Export — Licence, flair.ini Flag, and Transfer Speed Setup — FBX licence and ini prerequisites
- See also: FBX Export Crashes or Hangs Flair Classic — Flair crash on FBX export
Related Tutorials¶
▶ 00:36 — Demonstrating why roll mode must match: setting Roll Up before importing a 3-node camera
▶ 00:26 — Move Export window — roll mode must be set correctly before export to match node type
Revision History¶
| Date | Change | Editor |
|---|---|---|
| 2026-05-24 | Initial extraction | Tom D / Claude Code |