As of now, motion matching queries are always done on the first Motion Matching Animation Library of an AnimationPlayer. Being able to define logic to choose which anim library to run a query on, would simultaneously:
Improve query performance, since we can run queries on smaller datasets
Get better motion matching results, since we can better restrict the range of possible animations.
As of now, motion matching queries are always done on the first Motion Matching Animation Library of an AnimationPlayer. Being able to define logic to choose which anim library to run a query on, would simultaneously: