{{ wiki.title }}
{{ wiki.title }}
Motion Symphony
  1. Introduction and Overview
    1. Installing the Plugin
    2. Support and Bug Reports
  2. General
    1. Motion Snapshot
    2. Runtime Mirroring
    3. Runtime Mirroring (DEPRECATED)
    4. Motion Snapshot (New)
  3. Motion Symphony 2.0 Update
    1. How To Update to 2.0
    2. New Features Quick Start
    3. Deprecations
  4. Motion Matching
    1. Understanding Motion Matching
    2. Caveats and Limitations
    3. Pipeline Overview
    4. Motion Configuration Asset
      1. Match Feature | Trajectory 2D
      2. Match Feature | Trajectory 3D
      3. Match Feature | Distance
      4. Match Feature | Momentum 2D
      5. Match Feature | Momentum 3D
      6. Match Feature | Momentum Rot
      7. Match Feature | Bone Loction
      8. Match Feature | Bone Velocity
      9. Match Feature | Bone Location & Velocity
      10. Match Feature | Bone Facing
      11. Match Feature | Bone Height
      12. Match Feature | Bone Axis
    5. Motion Calibration Asset (Optional)
    6. Motion Data Asset
      1. Initial Setup
      2. Adding Animations
      3. Configuring Animations
      4. Tagging
      5. Pre-Processing
      6. Preview and Debugging
      7. Optimisation
    7. Input Response Data
    8. Trajectory Generation
      1. Trajectory Generator Component
      2. Trajectory Generator - Event Graph
      3. Debugging
      4. Input Profiles
      5. Custom Trajectory Generator Component
    9. Motion Snapshot & Inertialization Nodes (Runtime)
    10. Motion Matching Node (Runtime)
      1. General Settings
      2. Pose Favour
      3. Pose Tolerance Test
      4. Input Response Blending
      5. Debugging
    11. Trajectory Error Warping
    12. Advanced Topics
      1. Blend Spaces
      2. Custom Pre-Process Tags
      3. Motion Tags
      4. Custom Match Features
  5. Pose Matching
  6. Multi-Pose Matching
  7. Transition Matching
  8. Distance Matching
    1. Distance Matching Node
    2. Distance Matching Component
    3. Animation Modifiers
  9. Foot Locking
    1. Understanding Foot Sliding
    2. Foot Locking Node
    3. Foot Locking Component
    4. Anim Notifiers (Foot Locking)
  10. How To's
    1. Strafe Motion Matching
  11. F.A.Q
Motion Tags {{ currentPage ? currentPage.title : "" }}

Motion Tags can be very useful as they enable the user to separate different animations or animation sections into different states using a set of GameplayTags stored in a GameplayTagContainer. At runtime, the user can specify a tag container at any given time (as node input) and the motion matching node will only ever play animations that exactly match the container.

To Tag Or Not To Tag

At the end of the day, tags are simply a different way of managing animation state. The same outcome could be achieved by simply creating a new state within your animation state machine. This would be easier to read, debug and understand. However, adding more states makes the graph more complex and difficult to manage. A balance is recommended and how you go about this is up to you.

Tagging animations can also be very helpful to better control animation. For example, you may even wish to tag start, stop and plant type animations so they are separated. However, the responsibility is then on you to trigger these tags when they should be active to achieve desired results.

Declaring GameplayTags

‘Gameplay Tags’ and ‘Gameplay Tag Containers’ are UE5 data types and they can be created in the project settings. Please see UE5 documentation for more details.

Adding Tags to Animations

There are two ways to add Tags to animations:

  1. Add them to an animation as a whole

  2. Add them via tags to specific sections of animations.

Creating And Managing Motion Tag Queries

In order to use motion tags at runtime, we need to manage a ‘Gameplay Tag Container’ variable adding and removing tags from it at runtime based on appropriate logic. For example, you may add the ‘walk’ tag when the player holds the button for walking and you may remove it when they release that button.

Create the Require Tag Query

Start by creating a variable in your animation blueprint of type ‘FGameplayTagContainer’. This will create an empty container which you use to store motion tags in an efficient manner.

Adding Motion Tags

Tags can be added to the container as shown below:

Removing Motion Tags

Tags can be removed to the container as shown below:

Feeding Motion Tags Into The Motion Matching Node

Once your motion tag query has been setup as you desire, it can be used as an input into any motion matching node via the ‘Required Motion Tags’ input / binding.

As your ‘Motion Tag Query’ is modified and changed in the event graph at runtime, the motion matching node will respond accordingly.

{{{ content }}}