# "Waiting for groom bindings to be ready"

**URL:** <https://forums.unrealengine.com/t/waiting-for-groom-bindings-to-be-ready/2400504>\
**Category:** Character & Animation\
**Tags:** bug, metahuman\
**Created:** [March 19, 2025, 10:40am UTC](https://forums.unrealengine.com/t/waiting-for-groom-bindings-to-be-ready/2400504 "2025-03-19T10:40:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SixelA\_EG](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/sixela_eg/32/1118994_2.png) [@SixelA\_EG](https://forums.unrealengine.com/u/SixelA_EG)\
**Post date:** [March 19, 2025, 10:40am UTC](https://forums.unrealengine.com/t/waiting-for-groom-bindings-to-be-ready/2400504/1 "2025-03-19T10:40:35Z")

</div>

Hi !

I got a similar problem as those, and would like some help because the solutions didn’t work for me. [Here](https://forums.unrealengine.com/t/unreal-freezes-when-modifying-groom-binding-assets-on-5-4-x/1965957/1) and [here](https://forums.unrealengine.com/t/solved-waiting-for-skinned-asset-to-be-ready-in-groom-binding-never-ends/1844735).

**“Waiting for groom bindings to be ready”**  
  
  
Whenever I tried to create a groom binding, or try to change the groom or target mesh from a binding that I duplicated, it freezes with this message…

I tried the solution here, but didn’t do anything for me. Even when I tried **“Editor.AsyncGroomBindingCompilation 2”** …  
  
  
I tried multiple things and I can say that the problem comes from using a groom that was not designed for metahuman (90% sure that’s the problem).

---

<div class="post-metadata">

**Author:** ![JonCable](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@JonCable](https://forums.unrealengine.com/u/JonCable)\
**Post date:** [January 30, 2026, 12:41am UTC](https://forums.unrealengine.com/t/waiting-for-groom-bindings-to-be-ready/2400504/2 "2026-01-30T00:41:09Z")

</div>

Try disabling async groom binding compilation. It’s in the editor preferences, or search for bEnableAsyncGroomBindingCompilation.

I’m pretty sure there’s a deadlock between the async groom bindings and the async skinned asset compilation systems, and it’s been around since 5.4. Hopefully making one of them not async works around it. But the issue is very sporadic for me so it’s hard to know if this helps yet.

Note, setting one of the AsyncXCompilation cvars to 2 will pause the system, and then setting it back to 1 resumes it. But I think once you’ve actually hit the deadlock it’s not going to help.
