> For the complete documentation index, see [llms.txt](https://docs.infimagames.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/editor/how-to-export-the-animations-from-unreal-engine-5.md).

# How to Export the Animations

Export the pack's animations as FBX files from Unreal Engine 5, so you can open them in Blender or another tool.

#### Table of Contents

* [Introduction](#introduction)
* [Before You Start](#before-you-start)
* [Export the Animations](#export-the-animations)
* [What Stays in Unreal](#what-stays-in-unreal)
* [Bringing a Clip Into Blender](#bringing-a-clip-into-blender)

***

### Introduction

***

In this guide I'll export the Pistol's reload from Unreal, the character clip and the weapon clip that goes with it. Any other animation works the same way.

{% hint style="info" %}
**Only need the files?** On the Fab product page, click **Download** and get `fbx_files_tacticalpistol.zip` or `fbx_files_tacticalassaultrifle.zip` under **Included formats**. It has every animation, the weapon meshes and their textures as FBX, without the character mesh. See [Using the FBX Files](https://docs.infimagames.com/product/tactical-fps-animation-packs/getting-started/quick-start-guide.md#using-the-fbx-files). The animation source files aren't included.
{% endhint %}

{% hint style="info" %}

#### Before You Start

* The pack is installed in your project.
* Know which action you want. The [Animation List](https://docs.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/reference/animation-list.md) has every clip, with the montage that plays it.
  {% endhint %}

***

### Export the Animations

***

{% stepper %}
{% step %}

#### Find the Character Clip

Export the animation sequences, the assets that start with `A_`. Montages and blend spaces don't export to FBX.

The character clips are in this folder, under `FP` or `TP`.

`Content/InfimaGames/TacticalFPSAnimations/Weapons/<Weapon>/Animations/Character`

For the Pistol's first person reload, that's `A_TFA_FP_Pistol_Reload` in `Character/FP/Combat`.

<div align="left" data-with-frame="true"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2Fw2FmPJLDZSRe0Ha4dXh8%2Fexport-01.png?alt=media&amp;token=12ff1947-f088-4da4-8340-a4859317a6cf" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Find the Weapon Clip That Goes With It

Most actions also have a weapon clip, on the weapon's skeleton. It has `WEP` in its name and sits in the `Weapon` folder.

For the reload, that's `A_TFA_FP_WEP_Pistol_Reload` in `Animations/Weapon/FP`.

<div align="left" data-with-frame="true"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2F3cex4DGJ2gsj1yBdprGO%2Fexport-02.png?alt=media&amp;token=6f11656c-03f0-4379-99fe-ed11f45eda30" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Start both clips on the same frame and they stay in sync. The animations are made in place, with no root motion.
{% endhint %}
{% endstep %}

{% step %}

#### Export to FBX

1. Select both clips.
2. Right-click and pick **Asset Actions > Export**.

<div align="left" data-with-frame="true"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2FfzzL9PlBogQyJtSbY0mk%2Fexport-03.png?alt=media&amp;token=4f64634d-fdbc-462e-a4e4-c70e4d689cab" alt="" width="470"><figcaption></figcaption></figure></div>

Then pick **FBX** as the file type and a folder, and click **Save**.

<div align="left" data-with-frame="true"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2FZ47sWrLXN89DvRPTjvkh%2Fexport-04-save-cropped-1112.png?alt=media&amp;token=9154ea28-2359-496e-9fc8-c04012f62b22" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Check the FBX Export Options

1. Tick **Export Preview Mesh** if you want the mesh in the file too.
2. Leave the rest as it is and click **Export**.

Unreal shows the save window and these options once per clip.

<div align="left" data-with-frame="true"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2F1YpMB1uibh9cdKWjhfv5%2Fexport-05.png?alt=media&amp;token=29774833-c91c-423c-9de5-1bc12103aef3" alt="" width="470"><figcaption></figcaption></figure></div>

{% hint style="info" %}
For many clips, pick **Asset Actions > Bulk Export**. It writes one file per clip and keeps the folder tree, and **Export All** uses the same settings for every clip.
{% endhint %}
{% endstep %}
{% endstepper %}

That's it! You now have the character clip and the weapon clip as FBX files.

***

### What Stays in Unreal

***

A sequence holds only the bone motion. These are added in Unreal, so they aren't in the file.

* **The notifies.** They sit on the montages. They hide and show the magazines, drop the empty magazine, eject the rounds, play the fire sounds and unlock the next action.

<div align="left" data-with-frame="true"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2FOK3ATLHAMTI21Hc7Mh7O%2Fexport-06.png?alt=media&amp;token=c5d9af57-6dff-470c-8fb2-618a80160f12" alt="" width="563"><figcaption></figcaption></figure></div>

* **The magazine.** Its own Animation Blueprint empties it round by round.
* **The Animation Blueprints.** Recoil, breathing, the aim transitions, canted aim, the grip poses, the left hand on the grip and the hand IK that keeps both hands on the weapon.

***

### Bringing a Clip Into Blender

***

Import the FBX with **File > Import > FBX**.

<div align="left"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2F4dWOm4xZE22Ivnv9eZfi%2Fexport-07.png?alt=media&amp;token=3779759e-d2f3-4729-9f1b-777a2bbafc11" alt="" width="563"><figcaption><p>An exported clip in Blender. The motion is baked as keys on every bone.</p></figcaption></figure></div>

The Blender source files on the Fab page are the weapon rigs and models. An exported clip is baked onto the bones, so it doesn't drive the rig's controls. To animate with them, start a new action on the rig. See [Using the Blender Source Files](https://docs.infimagames.com/product/tactical-fps-animation-packs/getting-started/quick-start-guide.md#using-the-blender-source-files).

<div align="left"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2FvXQLktCVUDUMfx9esR4s%2Fexport__blender_rig_pistol-1112.png?alt=media&amp;token=f18e38f7-deb2-40d1-8101-e133b658f3ae" alt="" width="563"><figcaption><p>The Pistol's Blender source file, the weapon rig with its bones around the moving parts.</p></figcaption></figure></div>

To bring a changed clip back into Unreal Engine, follow [How to Export Animations From Blender to Unreal Engine 5](https://docs.infimagames.com/product/rigged-gun-model-packs/learn/guides/how-to-export-animations-from-blender-to-unreal-engine-5) in our Rigged Gun Model Packs docs. The steps are the same.

Import onto the pack's own skeletons.

* The character's is `SKEL_TFA_Mannequin` in `Common/Characters/Mannequins/Meshes`.
* The weapon's is `SKEL_TFA_Pistol` or `SKEL_TFA_AR` in that weapon's `Meshes` folder.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/editor/how-to-export-the-animations-from-unreal-engine-5.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
