{{ 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
Input Response Data {{ currentPage ? currentPage.title : "" }}

Motion Symphony 2.0 is a generic system, meaning that it does not force a specific configuration like MS1.0, where a ‘Trajectory’ was the main input for controlling the motion matching node. In MS2.0 it is possible to use different input response data as well as multiple input response types and therefore the input into the motion matching node cannot just be a trajectory, it needs to be more generic.

For Motion Symphony 2.0 we use a generic data type called ‘FMotionMatchingInputData’ which is essentially is a wrapper for a float array containing all the data from all ‘Input Response’ type match features.

Setting Up

In your animation graph you will need to create at least one variable of type ‘FMotionMatchingInputData’. This data needs to be initialized with the ‘Motion Configuration’ you are using so that it has the correct size for your setup and then that data needs to be updated and filled every frame to provide the appropriate control from the player to the motion matching node.This data can be filled via specific components depending on the type of ‘Input Response’ match features you are using. For example, if you use a ‘Trajectory 2D’ match feature, you can use the Trajectory Generator Component to automatically fill this input data. Follow these steps to adequately initialize and fill your input data at runtime.

Note: Since the Input Data is essentially a wrapper for an array of floats, it is technically possible to fill the data manually with any input response data. However, this method is only for advanced use cases. For the majority of uses, the data should be automatically populated with the available helper functions.

Step 1: Create a variable in your animation graph of type ‘MotionMatchingInputData’.

Step 2: In the ‘Update Animation Event’ use the helper function ‘ConstructMotionInputFeatureArray’ to fill the ‘InputData’ automatically depending on the available components and ‘MotionConfiguration’. This is shown in the below image:

Note: If you do not have the appropriate components attached to your character, this function will just fill the data as zero. Make sure you have the necessary components attached. See the next section for details.

Step 3: Use the Input Data as an input for your Motion Matching node/s:

Note: It may be appropriate to use different InputData for different animation nodes depending on your project. You are not limited to one. Essentially you want to have one InputData for every different ‘Motion Config’ you are using.

Components Required for Automatic Input Data Construction

In order for the ‘ConstructMotionInputFeatureArray’ blueprint function to work, it needs to be able to extract relevant data from components attached to your character, otherwise the data will just be ‘zero’ filled. This section describes which components are required for each ‘response type’ match feature to function.

Trajectory Generator

The ‘Trajectory Generator’ component is required for the following match features to work:

  • Match Feature Trajectory 2D

  • Match Feature Trajectory 3D

Distance Matching

The ‘Distance Matching’ component is required for the following match features to work:

  • Match Feature Distance

Character Movement

The ‘Character Movement’ component is required for the following match features to work:

  • Match Feature Body Momentum 2D

  • Match Feature Body Momentum 3D

Manually filling the Input Data

In some edge cases it may be desirable to manually fill the input data array or modify it. However, this is an advanced topic and should not be attempted unless absolutely necessary as the process is prone to error. Even in the case of custom ‘response type' match features, it is better to override the ‘SetInputData’ function on the custom match feature itself rather than filling the data manually.

Since the ‘MotionMatchingInputData’ type is just a wrapper for a float array, one can simple access the float array named ‘DesiredInputArray’ within the input data and modify it directly. In order to do so you must understand how the data is laid out for match features.

Data Layout

‘Input Data’ is laid out sequentially in order of the ‘response type’ match features listed in the ‘Motion Configuration’. Different match features have different sizes, and this must be taken into consideration. ‘Match Feature’ sizes can be seen on the pages for each match feature individually.

For example, consider a motion configuration as such.

The data will be laid out with all Trajectory 2D data first followed by the Distance Matching Data. In this case, it’s obvious to see that the data for each match feature will be as follows:

  • Trajectory 2D: Index 0 to 11

  • Distance Matching: Index 12

To see how the data is laid out within each specific match feature, see the specific pages on each match feature. As an example the complete data layout for the described motion configuration would be as follows

PosX_0 | PosY_0 | FaceX_0 | FaceY_0 || PosX_1 | PosY_1 | FaceX_1 | FaceY_1 ||      
PosX_3 | PosY_3 | FaceX_3 | FaceY_3 || Distance ||

{{{ content }}}