Since updating to 5.8, and persisting through 5.8.1 and 5.8.2, we’ve been seeing this warning during cooking:
UPoseSearchLibrary::MotionMatch - some searches have been skipped, since databases AsyncBuildIndex are in still in progress or failed
We are mostly using the animation and rigging from Animation Sample Project, but have some of our own as well.
There is nothing in the logs that hints at what assets are related to the warning, and trying to work backwards from the warning has been pretty fruitless.
Are there some general things we should be checking to see what would cause this? This is the only warning we have not been able to eliminate as part of our 5.8 upgrade.
Hi, it’s unusual to see that warning generated during cook so I’d need a bit more information to track down what’s going on. Generally, we don’t expect the MotionMatch function to be invoked during cooking. Are you running the cook from a commandlet or the editor? And would you be able to supply a call stack for when the message is generated?
Ok yeah, I don’t see anything that should be forcing a regular motion matching search during cook from a commandlet. One possibility is that it’s the USkeletalMeshComponent::OnRegister method that’s calling USkeletalMeshComponent::TickAnimation, which might be causing the search. If you haven’t already, you could try setting bTickAnimationOnSkeletalMeshInit to false to see if that changes the behaviour - we generally recommend disabling this flag for performance reasons, but it does cause ref-pose to be displayed on the frame that a mesh is spawned, which then has to be hidden)
Also, are you using the pose search column within chooser assets at all? That’s another bit of functionality that could potentially cause a search outside of the usual anim instance update.
Generally though, if you’re able to get a callstack it should make it easier to track down where this is coming from.
TIL there’s a way to dump the stack to log:
posesearch.log(16.6 KB)
We are cooking via commandlet from Horde, using the built-in <Cook> task.
I can see about getting a call stack, but it will probably take me a while to find the time. We almost entirely rely on Horde + zen for cooking.
It’s possible that there is some custom plugin that is accessing the pose search DB unexpectedly when commandlet is run, but that has not been obvious since we do not get this when working with Editor.
bTickAnimationOnSkeletalMeshInit was exactly it! We shouldn’t have any problems flipping this to off by default.
Thanks!
Perfect, thanks for letting me know that fixed things! It’s also good to know on my side that was the cause, in case this comes up again in the future. Anyway, I’ll close out this thread now we have a resolution.