public sealed class AnimationClipImporterCompiles a .vxanim into the artefact a build loads.
No guide page documents this yet — the page shows what the code says about itself.
As a importer
- Extensions
- .vxanim
Remarks
What this closes. A .vxanim used to go through NativeFormatImporter, which carries the YAML text forward unchanged — enough for the reference scan and for the editor to open the file, and not enough for a game to play one. Nothing turned the authored curves into the AnimationClipData that Create bakes against a skeleton, so no clip could be loaded by address. .vxscene, .vxmat and .vxcompositor had all made this move already; this is the same move.
The curves are sampled here rather than at load. Baking is the pipeline's job and it happens once; a build that shipped tangents would evaluate the same Hermite segments on every machine that ever plays the clip. What ships is AnimationClipContent — channels, events, wrap mode and any metadata this build did not interpret.
⚠ The written type string is AnimationClipContent's alias, and the old one was not any type's. NativeFormatImporter wrote these bytes under "AnimationClip" — the name of the runtime class, which is not what the bytes are and which nothing could have resolved. It never surfaced because no project had ever loaded a clip at run time. This is the third occurrence of that mistake in this pipeline after "Material" and "Mesh", and the first one a loader will actually meet.
Fields and properties (2)
public const string ClipTypeThe alias of the type this writes. The compiled clip, not the authored one.
public override int Version
Methods (1)
protected override ValueTask<ImportResult> ImportAsync(ImportContext context, AnimationClipImportSettings settings, CancellationToken cancellationToken)Imports one asset.
Used by (4)
- AnimationClipImporterTestsVixen.Editor.Assets.Tests
- BuiltInImportersVixen.Editor.Assets
- ClipMetadataTestsVixen.Editor.Assets.Tests
- ConstraintAuthoringImporterTestsVixen.Editor.Assets.Tests