{{ 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
Trajectory Generator - Event Graph {{ currentPage ? currentPage.title : "" }}

In order for the trajectory generator to work, the player input (or AI input) needs to be fed into the trajectory generator every frame or at specific time intervals (e.g. 30Hz).

Setting Trajectory Input

Below is a simple example of how to set the trajectory input on Tick.

Note: This is only an example, you don’t have to perform this on tick. It could be at certain time intervals (e.g. 30Hz) and the method of getting your input values can differ.

How you get your movement input and call this function is up to you and you may wish to do it differently.

Make the Trajectory Camera Relative

For player controlled characters, it will often be desirable to make the trajectory generate relative to the camera Yaw rotation. This is done by simply transforming the input vector relative to the camera yaw. Motion Symphony provides a utility function to perform this, but you could do it any way you like as an alternative.

Changing Trajectory Generator Settings At Runtime

It may be necessary at times to change settings on the trajectory generator like the ‘Max Speed’ or responsiveness values. The relevant settings are exposed to blueprint and can easily be changed at runtime as follows.

This example is shows a simple input based hold for walk and release for run. When walking the max speed is reduced to 200 and when running it is reset again to 400.

Trajectory Replication

The very first step of replicating motion matching is to replicate the input vector to the trajectory generator as this is the primary input into the motion matching system. In short this is the order of things:

  1. Controlling Client Predictively Sets the Trajectory Input Vector

  2. The input vector is then sent to the server

  3. The server multi-casts the input vector to all clients where the input vector is set. In the case of the controlling client, the input vector does not need to be set as it was already predicted. Some validation may be preferential. here.

{{{ content }}}