An animated character should be checked before it goes into the engine, not after. A badly named clip, a skeleton exported at the wrong scale or a pack that lacks the promised animation can be spotted in a minute when you know what to look for. Once the asset is imported, the same problem costs you a project clean-up. This guide gives you the checklist, and how to run through it on Mac with Eyemesh, without opening any content creation software.
It is one of the reflexes in our method for organising your 3D game asset library: knowing what an asset contains before deciding to use it.
An animated asset is three things stacked together: a mesh, a skeleton that deforms it, and one or more animations that move that skeleton.
joints). The specification also sets the unit: distances are in metres, and the +Y axis points up.What actually goes into the file depends on the export. In Blender's FBX exporter, for instance, with the All Actions option turned off, only the assigned action is exported. A pack advertised with ten animations may very well contain just one: that is exactly what the check should reveal.
Seven points cover most of the surprises.
| Point | What you check | Warning sign |
|---|---|---|
| Clips | The list of animations and their names | A single clip instead of ten, generic names |
| Duration | The length of each clip | A 30-second walk cycle, a 0-second clip |
| Loop | The join between the last frame and the first | A visible jump on every cycle |
| Skeleton | Whether there is a rig, and the bone count | No bones on a character that is supposed to be rigged |
| Hierarchy | The root and the bone names | Several roots, unreadable names or names that differ between files |
| Rest pose | The pose saved without animation | Twisted limbs, a pose that differs from one file to the next |
| Scale and origin | The real height and the pivot position | A 180-metre character, a model far from the origin |
Bone names deserve special attention if you plan to share animations between several characters: as you will see below, engines match bones from one file to another by their name and hierarchy.
Open the pack's folder in Eyemesh. Everything that follows happens in the viewer, with no import and no project.
In the grid, every file that contains animations carries a small orange running-figure badge on its thumbnail. In a pack of two hundred files, you know immediately which ones to examine.
Select an animated file: an animation bar appears at the bottom of the viewer. When the file contains several clips, a menu lists them by the name they have in the file. Switching clips loads the new motion, resets the timeline and shows its duration. For an FBX, each animation stack that actually animates the model becomes a clip; an unnamed stack appears as ‘Animation 1’, ‘Animation 2’…, which is in itself a good sign of a careless export.
The controls are described in detail on the animation playback page.
The bar shows the elapsed time and the clip's total duration, in seconds. Drag the timeline to stop on any frame: playback pauses while you inspect the pose. The speed goes from x½ to x1 or x2: half speed for a fast action, double speed to get through a long clip. Playback loops automatically, which shows straight away whether a walk cycle joins up cleanly.
Open the info panel with the ‘i’ button, Info tab. If the model has a rig, a Skeleton section appears, with the ‘Show bones’ switch. The skeleton is then drawn as a yellow wireframe, one octahedron per bone, visible through the mesh and animated in sync with it. It is the quickest way to spot a badly placed joint or a bone that heads off in an unexpected direction during a clip.
The same section shows the bone count and, under ‘Armature’, the full skeleton tree, expandable bone by bone. There you can read the root, the order of the limbs and the naming convention. Two characters meant to share the same animations should show the same tree.
The Dimensions section gives the width, height and depth, the centre of the bounding box and the origin offset. Eyemesh converts FBX files to metres, Y axis up, when it opens them: the height reads directly in metres. An adult humanoid should show a value close to 1.8. A height of 180 or 0.018 gives away a unit error at export.
For a character whose pivot is at its feet, the centre of the box sits at half its height, so an origin offset of around half the height is normal. An offset of several metres signals a model exported far from the origin, which will appear offset in the engine's scene.
The rest pose is checked on the character's file without animation, when the pack provides one: opened in Eyemesh, it shows up in the pose saved in the file, with the skeleton visible if needed. The list view then lets you compare the dimensions of all the characters in a pack at a glance.
Side-by-side comparison opens two files in two viewers, with linked cameras if you wish. Each side has its own animation bar: you can play the walk from version 2 next to the one from version 3, or compare the same clip on two characters. The guide to comparing two versions or LODs side by side explains the method in detail.
The check makes full sense once you know what the engine will do with the file.
The Rig tab of the import settings offers four animation types: None, Legacy, Generic for any non-humanoid rig, and Humanoid for a rig with two legs, two arms and a head. Unity usually detects the skeleton and maps it to the Avatar, but you sometimes have to set up that mapping by hand. The manual states that a Humanoid model has at least 15 bones. The bone count read in Eyemesh therefore tells you right away whether Humanoid mode is an option.
The Animation tab then lists the file's clips: the original takes can each be imported as a clip, with its loop setting (Loop Time). As for scale, the Convert Units option brings the file's unit in line with Unity's, where one metre equals one unit.
Unreal stores animations under a Skeleton asset. Several meshes can share the same Skeleton provided they have the same general hierarchy, with bones in the same order and under the same names. When importing an animation, Unreal matches its bones to those of the chosen Skeleton by name and hierarchy. That is why Eyemesh's ‘Armature’ tree is so useful before importing a second pack. Unreal's unit is the centimetre, and FBX import offers a conversion from the file's unit to the engine's.
Since Godot 4.3, the default FBX importer has been built on ufbx, the same library Eyemesh uses to read FBX files. The scene import settings let you choose whether to import animations, set the sampling rate, trim the start and end of clips where no keys change, and add a RESET animation built from the skeleton's rest poses.
Still unsure which format to deliver to your engine? The guide FBX, glTF or USD: which format for Unity, Unreal or Godot sets it all out.
Open the file in Eyemesh. When it contains several clips, a menu in the animation bar lists them by their original names. In the grid, an orange badge already flags the animated files before you even open them.
Open the info panel, Info tab. A Skeleton section appears if the model has bones, with their count and their tree. The ‘Show bones’ switch draws the skeleton over the model.
Unity's manual gives a minimum of 15 bones, organised like a human skeleton: two legs, two arms and a head. The bone count shown by Eyemesh lets you check this before importing.
Almost always because of a unit declared incorrectly at export. Eyemesh converts FBX files to metres when it opens them: if the height shown in the info panel is 180 instead of 1.8, the problem lies in the file, not in the engine.
Yes. Drag the timeline to stop on the pose you want; playback pauses during the inspection. The x½ speed also helps break down a fast movement.
Yes. Eyemesh reads animations from FBX, GLB, glTF, USDZ, DAE and Alembic files with the same animation bar, the same clip selector and the same skeleton display.
Open your animated packs in Eyemesh: clips, duration, speed, skeleton and dimensions, with no engine and no content creation software. 7-day free trial.