This prevents re-initialization pops if a non-active child still has weight, and is consistent with state machines
#jira UE-96588 - GitHub 7249 : Added an option to AnimNode_BlendListByBase to Allow for Re-initialization only when active child's weight is zero
#7249
#preflight 619d1e3e974d7d57269201f0
#rb Jurre.deBaare
#ROBOMERGE-AUTHOR: thomas.sarkanen
#ROBOMERGE-SOURCE: CL 18280962 in //UE5/Release-5.0/... via CL 18280997
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18281042 by thomas sarkanen in ue5-release-engine-test branch]
This represents UE4/Main @18073326, Release-5.0 @18081140 and Dev-PerfTest @18045971
[CL 18081471 by aurel cordonnier in ue5-release-engine-test branch]
Scoring weights can now be specified at several levels of abstraction.
Channel: Pose weight vs trajectory weight.
Horizon: History weight vs prediction weight.
Type: Weights per feature types, such as positions and velocities.
Weights are normalized at each of these levels. So ultimately the weights that
make up all channels of a weights group will sum to 1 (or zero if entirely disabled).
Several new concepts were introduced for this system that aren't fully
formalized. Channels aren't a concrete data type, but I'm imagining we'll head
in that direction where a Schema is made up of Channels which themselves contain
sampling paramters like time/distance offsets and what to sample. The weights
system sets itself up in such a way to effectively pretend channels exist.
Similarly, horizons aren't an explicit data type either and the weights system
pretends they sort of are for presenting this high level concept of past vs future
weight to the user.
I have removed the previous weighting system including per sequence weights.
This feature will be replaced by a grouping system for databases in the future.
Groups will be collections of sequences and a set of weights for that group.
This is why the WeightsContext contains an array of 1 group of weights-- it's
setup that way to vector the implementation toward groups.
Speaking of the WeightsContext, the motion matching node holds onto one and
updates it every frame. This is in order to support changing weights at
runtime. There are a set of dynamic weight parameters that can be used to scale
the weights of all weight groups within a database. The WeightsContext tracks
the prior dynamic weight params and knows if the weights buffer needs to be
recomputed or not. So most of the time, updating the WeightsContext is a no-op.
In the future we'll need to add support for interpolating changes to dynamic
weights to avoid abrupt scoring changes.
#preflight 614452dd568b3a00013ee9cb
#rb cesar.castro
#jira none
#ROBOMERGE-AUTHOR: braeden.shosa
#ROBOMERGE-SOURCE: CL 17555406 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v870-17433530)
[CL 17555422 by braeden shosa in ue5-release-engine-test branch]
Included features in this changelist:
* Capture a snapshot of common movement properties (velocity, speed, etc) that are used to drive animation
* Character movement component for stop/pivot location
* Library of anim node functions for Distance Matching
* Template anim node that can advance by distance traveled rather than by time
* Template anim node that's driven by distance to a target rather than by time
* Animation modifier that generates distance curves based on root motion
* Turn in place functionality for keeping the capsule from spinning the pose when it rotates by applying an offset, includes functionality for turn on spot animations to compenstate for the offset
#preflight 61446e46599fd80001c250e2
[at]Koray.Hagen, [at]Thomas.Sarkanen, [at]Fernando.Coello
[FYI] Laurent.Delayen
#ROBOMERGE-AUTHOR: aaron.cox
#ROBOMERGE-SOURCE: CL 17551436 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v870-17433530)
[CL 17551464 by aaron cox in ue5-release-engine-test branch]
#rb braeden.shosa, aaron.cox, cesar.castro
#jira none
Motion Trajectory Component for Motion Matching:
Motion Trajectory Component notes:
1) Abstract component/interface implemented with prediction and history API.
2) Implemented uniform, frame-rate independent history sampling algorithm for retaining trajectory sample coherence.
3) Implemented concrete Character Movement Trajectory Component for encapsulating ground locomotion prediction algorithm and API.
4) Motion Trajectory blueprint library containing:
5) FlattenTrajectory2D algorithm for isolating and removing Z axis direction contribution from tracjectory.
6) ClampTrajectoryDirection for projecting trajectory samples into a discrete, allowed set of directions (such as cardinal).
Engine changes:
1) Implemented shared TrajectorySample, Range, and Domain structures for common usage among Motion Trajectory, Pose Search, and Blueprint.
2) Expanded Sequence Player blueprint library functionality for Scripted Motion Matching content example.
Pose Search changes:
1) Match Pose renamed to Pose History with minor configuration parameters.
2) Complete removal of approximated past trajectory sampling. This has now been pushed to the Motion Trajectory Component.
3) Motion Matching interface changes: Goal has been replaced with Trajectory and Dynamic Play Rate Adjustment has been encapsulated to an experimental code module and blueprint library. New defaults, and encapsulating settings.
4) Motion Matching changes: New Pose Search blueprint library which encapsulates core Motion Matching algorithm.
5) Unified Trajectory to Pose Feature Vector transformation algorithms.
6) Removal of temporary Pose Search Prediction blueprint library (now Dynamic Play Rate).
7) End-to-end implementation support for Past/Future Time and Distance domain schemas.
AnimInput changes:
1) Removal of AnimInput_CapsulePrediction (replaced with Motion Trajectory Component).
Gameplay Anim Gym changes:
1) Pose search database is now fully distance-based (history and future).
2) Character blueprint includes Character Movement Trajectory Component with distance-based domain setup.
3) Scripted Motion Matching anim node function prototype with Engine content example.
#preflight 6143ef4681695600011c49a8
#ROBOMERGE-AUTHOR: koray.hagen
#ROBOMERGE-SOURCE: CL 17547347 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v870-17433530)
[CL 17547352 by koray hagen in ue5-release-engine-test branch]
Also fixes type conversions (first time I have tried to convert to a base class and found that my IsChildOf check was the wrong way around).
Plus some extra accessors added for exec/update contexts.
Found the need for these when doing show & tell prep.
#rb Jurre.deBaare
#ROBOMERGE-SOURCE: CL 17367354 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v865-17346139)
[CL 17367419 by thomas sarkanen in ue5-release-engine-test branch]
Fixes anim task blocking on RB sim task and doing 0 work, now taskgraph schedules work and doesn't lock up extra threads.
#jira UE-120634
#rb chris.caulfield
#ROBOMERGE-SOURCE: CL 17083918 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v853-17066230)
[CL 17083927 by max whitehead in ue5-release-engine-test branch]
Crash using ControlRig in Sequencer
#info save/use cached pose nodes are not correctly invalidated/refreshed due to ControlRig edit mode invoking evaluation of the same anim instance multiple times per frame
#fix ensure that various counters used for synchronization/invalidation of cached data are used by ControlRigLayer proxy - and applied whenever update/evaluating the source "input" proxy
#ROBOMERGE-SOURCE: CL 16927983 via CL 16928005
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v838-16927207)
[CL 16928022 by jurre debaare in ue5-release-engine-test branch]
#info save/use cached pose nodes are not correctly invalidated/refreshed due to ControlRig edit mode invoking evaluation of the same anim instance multiple times per frame
#fix ensure that various counters used for synchronization/invalidation of cached data are used by ControlRigLayer proxy - and applied whenever update/evaluating the source "input" proxy
#rb Martin.Wilson
[FYI] Mike.Zyracki, Halfdan.Ingvarsson
#ROBOMERGE-SOURCE: CL 16922496 via CL 16926362
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v836-16769935)
[CL 16926740 by jurre debaare in ue5-release-engine-test branch]
For now, removing these as their semantics are due to change
Also converting Update and Become Relevant functions to use more-devived-typed update context (less casting required)
#rb Jurre.deBaare
#ROBOMERGE-SOURCE: CL 16771205 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v836-16769935)
[CL 16771237 by thomas sarkanen in ue5-release-engine-test branch]
- SetPreviewSkeletalMesh to UAnimationAsset and UAnimBlueprint
- Functionality to retrieve UAnimationGraphs and UAnimationGraphNodes of a specific class from UAnimBlueprint and UAnimationGraph respectively
- Functionality for pose driver/asset scripting
#jira UE-117797
#rb Thomas.Sarkanen
#preflight 60d075e32ab218000115936a
#preflight 60d1a3eaa819040001397a52
#ROBOMERGE-SOURCE: CL 16741838 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v835-16672529)
[CL 16741845 by jurre debaare in ue5-release-engine-test branch]
Split 'node context' into an 'evaluation context' and a 'node reference' type and updated regular function signatures when creating node functions. This way we can seperate concerns (and potentially reference anim nodes standalone in the future).
Moved function caller code into function ref file to stop AnimNodeBase bloat.
Fixed functions not being called on root nodes.
#rb Jurre.deBaare
#ROBOMERGE-SOURCE: CL 16727107 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v835-16672529)
[CL 16727111 by thomas sarkanen in ue5-release-engine-test branch]
