> For the complete documentation index, see [llms.txt](https://docs.motorica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motorica.com/documentation/integrations/unreal-engine/how-to-guides/import-single-animations-onto-import-plugin-skeleton.md).

# Import Single Animations Onto Import Plugin Skeleton

<figure><img src="/files/cQ1YG0nUW4CSdO71MJM9" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
This guide is only relevant if you have seen the error on the left image above, when trying to import an animation **directly** onto the skeleton that comes packaged with the plugin.
{% endhint %}

In UE 5.5, Epic introduced the new **Interchange** importer which altered the way that FBX importing happens in-engine. Our plugin uses a **Z-up** version of the skeleton, to be compatible with the engine's motion matching tools. Therefore, to import the **Y-up** animations that our platform generates, we must configure some input settings, but these settings do not exist in Interchange!

As a result, when importing animations directly onto `SKEL_Motorica`  (the Motorica skeleton that is packaged with the plugin) we get the artefacts seen on the left image at the top of this page.

## How to Fix

Before importing animations directly onto this skeleton, you must first use the console command:

<p align="center"><code>Interchange.FeatureFlags.Import.FBX 0</code></p>

This will **disable interchange** for all FBX imports, allowing you to use the legacy import procedure. After this, you may continue with the import process, first by clicking 'Import':

<div align="left"><figure><img src="/files/Z0mhxw495tXx858sIOge" alt="" width="563"><figcaption></figcaption></figure></div>

Then, select the file(s) you want to import, and you'll be greeted with the **legacy import options**. From here you will need to:

1. Select the Motorica Skeleton

<div align="left"><figure><img src="/files/EefCXXrkvzYqCNTfEFZd" alt="" width="521"><figcaption></figcaption></figure></div>

{% hint style="info" %}
*<mark style="color:$info;">If it doesn’t show up initially, you may have to click the settings cog and select 
‘Show Plugin Content’</mark>*
{% endhint %}

2. Select 'Use Default Sample Rate'

<div align="left"><figure><img src="/files/jjWDMxXrg7tNHMY3KCpZ" alt="" width="529"><figcaption></figcaption></figure></div>

3. Select 'Force Front XAxis' and set Import Rotation to `(0°,0°,90°)`&#x20;

<div align="left"><figure><img src="/files/HvL6yDpNAy5mbGOGcA6y" alt="" width="530"><figcaption></figcaption></figure></div>

4. Then you're done!

<div align="left"><figure><img src="/files/M9bebESnWQJvwhH67iqq" alt="" width="135"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
Don't forget to run `Interchange.FeatureFlags.Import.FBX 1`  to revert the console command & bring back the Interchange FBX importer for other assets!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.motorica.com/documentation/integrations/unreal-engine/how-to-guides/import-single-animations-onto-import-plugin-skeleton.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.