Workflows

Workflows automate multi-angle sprite sheet generation. Instead of manually rotating the camera and exporting for each direction, a workflow does it all in one pass — capturing every animation at every required camera angle and labeling each sequence automatically.

Available Workflows¶

How to Run a Workflow¶

1. Import your model and ensure animations are loaded.
2. Open the Workflows tab from the menu bar.
3. Select a workflow preset.
4. Configure output settings (frame size, FPS, export format).
5. Click Run Workflow.

The app will automatically rotate the model to each required angle, play through all animation clips, capture frames, and combine everything into the output format you chose.

Before each sequence, the workflow waits for the animation state to apply, moves the camera, lets the render view settle, then starts frame capture. You can cancel a running workflow; the active sequence capture is stopped before the workflow exits.

Workflow Camera Settings¶

Workflows use a camera draft that can be previewed before capture. Configure these settings in the workflow panel:

• Camera type — Perspective or Orthographic. The preview and final workflow capture use the selected type.
• Distance / zoom — Controls framing for the selected camera type.
• Elevation — Vertical camera angle for the preset or selected direction.
• Direction / rotation offset — Rotates the preset directions when you need a different facing convention.
• Target — The world-space point the camera frames.

Changing camera type updates the workflow preview, so you can compare perspective and orthographic output before running the capture.

Animation Selection¶

The workflow animation list controls which clips generate rows. Animations that are toggled off are skipped and do not create output rows when the workflow runs.

Use this list to hide noisy test clips, duplicate imports, or animations that should not be part of a production atlas. Hidden or disabled clips remain in the model; they are just excluded from workflow generation.

Force Animation In Place¶

Use Force animation in place when root motion would move the character through the frame during capture. This is helpful for walk/run cycles that should loop in place for game sprites.

The setting is part of workflow animation settings, so it applies to workflow capture and preview without changing the original model file.

Output Structure¶

Each animation clip is exported with direction labels appended to the clip name. For example, a model with idle and walk animations run through Top-Down 8-Dir produces:

idle_N
idle_NE
idle_E
idle_SE
idle_S
idle_SW
idle_W
idle_NW
walk_N
walk_NE
...

These labeled sequences are embedded in the exported JSON/metadata file so your game engine can look them up by name. Workflow exports also include structured direction metadata: each sequence records its base animation and direction, and directionalAnimations groups rows like walk_N, walk_E, walk_S, and walk_W under the shared walk animation.

Tips¶

• Name your animation clips clearly in your 3D tool before exporting — those names become the sequence identifiers.
• For isometric games, the Isometric workflow produces the four standard angles (SE, NE, NW, SW) used by most isometric engines.
• The Platformer workflow captures both Right and Left directions. Use Platformer Single Side if your game will mirror the sprite at runtime.
• Enable Capture normal maps before running a workflow if you want every workflow sequence to include real normal map frames.
• Workflows respect your current lighting and effects settings — configure those first.
• Toggle off any animation clips you do not want before running the workflow; disabled clips are not exported as rows.