{{ 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
Custom Pre-Process Tags {{ currentPage ? currentPage.title : "" }}

While it is probably not necessary for most users, it is possible to create custom tags in blueprint or C++ to use on motion matching animations in the MotionData editor. These tags only run during the pre-processing phase and they can be used to modify the animations they are placed on and the poses that they encompass.

Note: Custom Pre-Process Tags is a very advanced topic and it requires knowledge of the inner workings and data structures of Motion Symphony. It is recommended that this feature is only for advanced users.

Creating a Custom Pre-Process Tag

There are two types of pre-process tags that can be created:

  • Tag Point - a tag that is specified at a specific point in time in the animation

  • Tag Section - a tag that encompasses a time ‘range’ within the animation

The choice of tag is dependent on the use case for your tag. The only difference is that the tag section modifies multiple poses within it’s range while the point is more for setting up interest points within an animation.

Step 1: Right click in your content browser and create a new ‘Blueprint Class’

Step 2: Search for Tag Point or Tag Section and pick one of them as your base class. A new asset will be created, name it as you like.

Tag Points

Tag points are tags that mark a specific time within an animation. They can modify and affect the animation itself based on the time of that tag. This is often used for baking data relative to that point. An example use case within Motion Symphony is the Distance Matching markers which bake data relative to a point in the animation.

A tag point blueprint has only a single function to implement and it is called only once for each tag point:

  • Received_PreProcessTag

Received_PreProcessTag

This function is called once for each TagPoint. In this function you have access to the following data via input parameters:

  • Point Pose - The closest pose to the tag (modifiable)

  • Out Motion Anim - The animation that this tag has been placed in (modifiable)

  • Out Motion Data - A reference to the entire Motion Data asset (modifiable)

  • Time - The time of the Tag Point in the animation

Tag Sections

Tag Sections are tags that cover a time range. They can modify and affect all poses within their time range.

A tag section blueprint has two functions which can be overwritten to run custom logic:

  • Received_PreProcessPose - Called once for each pose within the tag section range.

  • Receieved_PreProcessTag - Called one time for the tag itself.

Received_PreProcessPose

This function is called once for each pose within the tag section range. In this function you have access to the following data via input parameters:

  • Out Pose - the pose that this function was called for (modifiable)

  • Out Motion Anim - The animation that this tag has been placed in (modifiable)

  • Out Motion Data - A reference to the entire Motion Data asset (modifiable)

  • Start Time - The starting time of the tag section range

  • End Time - the ending time of the tag section range

Received_PreProcessTag

This function is called once each tag. In this function you have access to the following data via input parameters:

  • Out Motion Anim - The animation that this tag has been placed in (modifiable)

  • Out Motion Data - A reference to the entire Motion Data asset (modifiable)

  • Start Time - The starting time of the tag section range

  • End Time - the ending time of the tag section range

Example Custom Tag

The below image shows an example custom tag which modifies the ‘cost multiplier’ of a pose based on a curve sampled at the time of the tag. This tag only needs to implement the PreProcessPose function.

Custom Tags in C++

For C++ users, custom tags can be created by inheriting from UTagPoint and UTagSection. Please see the source code for existing tags for an example on how to achieve this.

{{{ content }}}