ACT in My Blender Workflow: Pivots, Names and Cleaner Unity Exports

Some of the Blender tools I value most do not change how a model looks. They make the handoff less repetitive. ACT: Game Asset Creation Toolset is one I use for setting pivots, exporting FBX files for Unity, organizing UV map data and keeping object and collection naming under control.

Pivot first, placement secondACT's origin tools can align an origin to minimum, maximum or middle points along an axis, or to the 3D cursor. That makes pivot setup easier to approach consistently across a group of assets. The official extension page documents these options.

My design check is where the asset should be handled from. A floor-standing prop, a modular wall and a rotating part do not necessarily want the same pivot. The shortcut helps perform the operation; the intended placement or movement still decides the location.

Exporting to Unity: the profile mattersI use ACT for Unity FBX output. The part worth checking carefully is which Unity profile is selected. The developer's export documentation distinguishes Unity from Unity (Pre-Rotated). The Unity profile requires “Bake Axis Conversion” in Unity's model import settings. The pre-rotated path avoids that step but has limitations, including animation and shared mesh data.

My practical rule is to test one representative asset before a batch: scale, orientation, pivot, hierarchy and animation where relevant. Exporting a hundred files quickly is useful only after the first file behaves correctly.

UV layers and names are part of the assetACT supports batch UV-layer operations by index and utilities for object and collection names. These are useful for the organizational work I do around a model. I want the exported asset to be understandable without someone reopening the entire Blender scene to guess what each part means.

A useful trap to avoid: renaming a UV layer “Lightmap” does not make its layout suitable for lightmapping. I would still inspect overlap, padding and the channel the engine actually uses. Likewise, adding an LOD suffix is an organizational step, not a substitute for creating and validating the lower-detail mesh.

The small check I recommendKeep a tiny import-check scene in Unity. Drop in the exported asset, rotate it, place it beside a known-size reference and inspect its materials and UV channels. For moving parts, test the intended motion. This catches the kind of mistake that looks harmless in a file list but becomes frustrating during scene assembly.

For me, ACT belongs in the practical part of the workflow: fewer repeated setup actions, clearer asset organization and a more deliberate handoff. The useful automation is the operation I already understand well enough to verify.

Tool note · 7 October 2026. ACT use described here covers my pivot, Unity FBX, UV-data and naming workflow. Feature details are linked to the extension developer's documentation.