Update on UE4 Version Compatibility and Usage - New FAQ - MoCap Online

Unreal Engine Version Compatibility FAQ | MoCap Online Packs

MoCap Online Packs & Unreal Engine: The Definitive Compatibility FAQ

This FAQ covers the most common questions we get about using MoCap Online animation packs in Unreal Engine — covering UE4, UE5, FBX import, retargeting, and everything in between. If you've ever wondered "will pack X work in UE 5.4?" or "do I need to retarget?", this is the doc for you.

Short answer: Yes, all MoCap Online animation packs work in every current version of Unreal Engine. The method you use to get them in depends on your situation. Details below.

Most of our packs are built for Unreal Engine 4 animation workflows, with full UE5 compatibility via retargeting.

Do MoCap Online Packs Work in UE5?

Yes. Every MoCap Online animation pack works in Unreal Engine 5.x. Our packs were built on the UE4 SK_Mannequin skeleton, and UE5 has full backward compatibility with that skeleton hierarchy. You have two paths to get our animations into a UE5 project:

  1. FBX Import (recommended) — Import the source FBX files directly into your UE5 project. This works in any engine version, period. Details in the FBX Import section below.
  2. Migrate from a UE4 project — Open the pack in its native UE4 version, then use UE4's Migrate function to copy assets into your UE5 project's Content directory. UE5 will convert them on load.

Once the animations are in your UE5 project on the SK_Mannequin skeleton, you retarget them to UE5's SK_Mannequin (or your custom character) using the IK Retargeter — UE5's replacement for the old Retarget Manager. More on that in the retargeting section.

For a complete walkthrough, see our dedicated guide: How to Use Motion Capture Animations in Unreal Engine 5.

UE4 Forward Compatibility (The Migrate Workflow)

Our UE4 animation packs are forward compatible using the Migrate function. This means a pack built in UE4.14 can be migrated into a UE4.27 project (or UE5, as noted above). The process:

  1. Open the pack in its native engine version. If you purchased from the UE Marketplace, create a blank project at the compatible version listed in the Vault, then add the pack to that project. If you purchased from MoCap Online, double-click the .uproject file to open it in its native version.
  2. In the Content Browser, right-click the pack's top-level folder (e.g. "Zombie_01") and choose Migrate...
    UE4 Migrate context menu showing the Migrate option
  3. Click OK to confirm the asset list.
  4. Browse to the Content directory of your target project (whatever engine version you want the animations in). Click OK.
  5. Open the target project. The animations are now available on the SK_Mannequin skeleton in your newer engine version.

Important: Migrate works forward (older → newer) but typically does not work backward (newer → older). This is an Unreal Engine limitation, not specific to our packs. If you need animations in an older engine version, use the FBX import method instead.

FBX Import Method (Works in Any Engine Version)

Every MoCap Online pack includes source FBX animation files. These can be imported into any version of Unreal Engine — UE4.8 through UE5.5 and beyond. This is the most universal method and the one we recommend for most workflows.

  1. Open your UE project. You need a compatible skeleton in the project — either the standard UE4 SK_Mannequin, or import our included SK_Mannequin FBX mesh first.
  2. Create or navigate to the folder where you want the imported animations.
  3. Drag the FBX animation files from your hard drive into the Content Browser. They're in the pack's Source/FBX folder.
  4. In the Import dialog: do not import the mesh. Set it to Skeleton only and choose the UE4_Mannequin_Skeleton already in your project. Click Import All.
    FBX Import dialog showing skeleton-only import settings
  5. Click Save All to save the imported animations.

That's it. The animations are now in your project on the SK_Mannequin skeleton, ready to use directly or retarget to your character. For a deeper dive into FBX workflows in Unreal, see our FBX Animation Guide.

Retargeting: UE4 vs UE5

Once our animations are in your project, you'll likely want to retarget them to your own character. The workflow depends on which engine version you're using.

UE5: IK Retargeter

UE5 replaced the old Retarget Manager with the IK Retargeter system. This is actually a significant improvement — it's more flexible, handles proportion differences better, and gives you fine-grained control over how motion transfers between skeletons. The basic workflow:

  1. Create an IK Rig for the source skeleton (our SK_Mannequin) and one for your target skeleton.
  2. Create an IK Retargeter asset that maps between the two IK Rigs.
  3. Adjust chain mappings and pose alignment as needed.
  4. Batch retarget your animations.

Our Animation Retargeting Guide walks through this in detail.

UE4: Retarget Manager

In UE4, retargeting uses the Retarget Manager on the Skeleton asset. You set up a humanoid rig mapping, configure the retarget source pose, and use "Retarget Anim Assets" or "Duplicate and Retarget" from the context menu. This system still works in UE4 projects but is considered legacy. If you're starting a new project, UE5's IK Retargeter is the better path.

For the full UE4 Retarget Manager walkthrough, see our A-Pose / T-Pose Conversion guide.

A-Pose vs T-Pose

This comes up constantly, so let's get into it.

Most of our current packs use a T-Pose as the retarget reference pose for the SK_Mannequin. This is different from Epic's default A-Pose. A small history lesson (stay awake, class):

When Epic released the improved SK_Mannequin for UE4.8, it shipped with the mesh skinned in an "A" pose — arms angled down to match the sculpted mesh. But the skeleton itself is technically in a "T" pose with all bones at zero rotation. Unreal imports skeletal meshes in the bind pose regardless of bone rotations, which is why the default mannequin appears in the "A" even though the raw skeleton data says "T".

The "correct" pose is a matter of opinion and workflow preference. Many of our older packs defaulted to T-Pose because that's what the majority of users were asking for at the time. In UE5, the distinction matters less because the IK Retargeter handles pose differences during the retarget setup — you align the source and target poses visually in the retargeter, and the system compensates.

Bottom line: Don't stress about A vs T. In UE5, configure your IK Retargeter's source preview pose to match what our animations expect, and you're good. In UE4, use the Retarget Manager to set the appropriate reference pose on the skeleton.

Weapon Bones ("wep" Bones)

Some of our packs — particularly the combat and weapon animation sets — include custom "wep" (weapon) bones as children of the hand bones. These bones are animated to position rifles, pistols, and other held objects, and come with sockets already configured in our pack projects.

A few things to know:

  • Migrate preserves wep bones and sockets. If you use the Migrate method, everything transfers.
  • FBX import does not preserve sockets. The bone hierarchy imports, but you'll need to recreate the sockets in your project if you need them.
  • Wep bones are being phased out. Our newer packs attach weapons to the middle finger bone (middle_01) with pose adjustments instead of using custom bones. This keeps the SK_Mannequin skeleton completely standard and maximizes compatibility. If you're importing an older pack that has wep bones into a project that doesn't, you'll see a dialog about missing bones being added — this is normal and won't affect your existing animations.

Reference Skeletons and Downloads

We include both A-Pose and T-Pose versions of the SK_Mannequin FBX with our packs. If you need standalone reference skeletons for testing or project setup, they're included in our Free Animation Pack — download it and you'll have everything you need to verify compatibility before purchasing.

Common Questions

"Will Pack X work in UE 5.4 / 5.5 / etc.?"

Yes. All MoCap Online animation packs work in all current UE5 versions. Use FBX import for the most direct path, or Migrate from the pack's native UE4 version. Either way, you'll end up with the animations on the SK_Mannequin skeleton in your project.

"Do I need to retarget?"

If your character uses the SK_Mannequin skeleton (or a derivative), you can use our animations directly with no retargeting. If your character has a different skeleton, yes, you'll need to retarget. In UE5, this means setting up IK Rigs and an IK Retargeter. In UE4, use the Retarget Manager. See our Retargeting Guide for the full process.

"I bought on the UE Marketplace but the Vault says it's for an older engine version. Is it broken?"

No. The Vault version label just indicates the engine version the pack was packaged for. The animations inside are engine-version-agnostic — they're skeletal animation data on a standard skeleton. Use the Migrate workflow to bring them into any newer engine version, or use the included FBX source files to import directly.

"What's the difference between buying from mocaponline.com vs the UE Marketplace?"

The animation content is identical. Packs purchased from MoCap Online include the full UE4 project plus source FBX files as a download. Marketplace purchases install through the Launcher Vault. Both give you the same animations — the difference is delivery method. Our store also offers bundle deals and format options (FBX, BIP, etc.) that aren't available on the Marketplace.

"Can I use these animations with MetaHuman?"

Yes. MetaHumans use a skeleton that's compatible with UE5's retargeting system. Import our animations onto the SK_Mannequin, then use the IK Retargeter to transfer them to the MetaHuman skeleton. Epic provides IK Rig assets for the MetaHuman skeleton that make this straightforward.

"Do I need to set up Animation Blueprints?"

Not to use the animations, but you will if you want blending, state machines, or any runtime animation logic. Our Animation Blueprints Guide covers how to integrate mocap animations into a proper Animation Blueprint setup.

---

Questions not covered here? Email us at MoCap@MotusDigital.com. We answer every one.

- Crispin

Get Professional UE Animation Packs

Browse MoCap Online's Unreal Engine animation packs — professionally captured, cleaned, and packaged for direct use in your UE project.

Related Articles

Migrating UE4 Animation Projects to UE5: Animation-Specific Compatibility Considerations

UE4 animation projects migrated to UE5 encounter predictable compatibility points that require specific attention beyond the standard migration procedure. The most significant is the skeleton compatibility change: UE5 introduced the UE5 Mannequin with a revised joint hierarchy that differs from the UE4 Skeleton primarily in the spine and clavicle chain structure. Animation clips that were purchased or created for the UE4 Skeleton play correctly on UE4 Skeleton characters in UE5 — backward compatibility with the UE4 Skeleton is maintained — but they do not automatically work on UE5 Mannequin characters. If the migration target is a UE5 Mannequin character, the animation assets require either retargeting from the UE4 Skeleton to the UE5 Mannequin using the IK Retargeter, or replacement with equivalent packs built natively for the UE5 Mannequin skeleton.

Animation Blueprint nodes that reference deprecated UE4 systems surface as compile errors or warnings in UE5 migration. The UE4 AnimDynamics node and UE4's single-chain IK solver have been supplemented (not fully replaced) by UE5's Control Rig integration and improved IK solver architecture. Animation Blueprints that use the legacy nodes continue to compile and function in UE5, but they do not benefit from UE5's performance improvements to the IK system. For long-term UE5 projects, migrating critical Animation Blueprint nodes from legacy UE4 implementations to UE5-native equivalents is worth scheduling as a dedicated pass during or after the initial migration. The visual logic in both cases is similar; the migration is primarily a node replacement rather than a logic redesign.

Asset redirector accumulation is a common post-migration maintenance issue that appears gradually rather than immediately. When animation assets are renamed, moved, or replaced during migration, UE5 creates redirectors that preserve old references. Redirectors allow existing content to function while pointing to the new asset location, but they add indirection that slows cook times and increases project complexity over time. Running the "Fix Up Redirectors" tool in the Content Browser after a migration stabilization period — once all renamed assets have been confirmed working at their new paths — removes accumulated redirectors and cleans up the project structure. For projects with large animation libraries, this step measurably reduces Cook and iteration times and is worth scheduling as a routine cleanup step after any large asset reorganization, migration, or batch import of new animation packs.