With the 5.7 update I started receiving FPoseSearchModule::Search, missing IPoseHistory errors to some of my movement actions from animation side. Does anyone knows about it and what is possibly causing it?
Before, Pose Search was strictly checked based on whether the Animation Blueprint had Motion Matching enabled. With the 5.7 update : now checking the Skeletal Mesh has Motion Matching enabled.
This means if a skeleton is shared, some animations can trigger PoseSearch even in AnimBPs that don’t use Motion Matching, which is not great imo.
It’s no longer local, it’s generalized.
In my case I have 2 view models:
They share the same skeleton to reduce animation authoring and overall load, and this worked fine before.Now the system effectively forces separate skeleton assets, even though asset-wise they could be identical.
Alternatively, we can just add a PoseHistory that does nothing, purely to tell the engine things are ok
That works, but it’s not very nice.
This seems like a regression in locality: Pose Search used to be scoped to the AnimBP, but in 5.7 it behaves as if it’s scoped to the skeleton.
If Pose Search exists anywhere on a skeleton in UE 5.7, the engine expects it to exist everywhere.
