Waiting groom bindings to be ready

Hello,

In our project, we currently have a large number of Groom Binding Assets, and we are experiencing extremely long loading times when opening maps that reference many of them.

When loading these maps, users frequently see messages in the loading pop-up such as:

“Waiting groom bindings to be ready 14/268(GroomBindingName)”

In some cases, it can take up to one hour before all Groom Binding Assets are ready and the map becomes fully usable.

We would like to know whether there are recommended ways to optimize these loading times.

In particular:

  • Can Groom Binding data be efficiently cached and shared through the DDC?
  • Are there specific DDC settings or workflows recommended for Groom Binding Assets?
  • Is there a way to precompute or prebuild the required binding data so that users do not have to process it locally when opening a map?
  • Are there any other recommended approaches for projects using a large number of Groom Binding Assets?

Any guidance on how Groom Binding Assets are cached and processed internally would also be very helpful for us to better understand where this loading time is coming from.

Thank you.

[Attachment Removed]

Steps to Reproduce[Attachment Removed]

Hi!

Groom binding are already build and cached through DDC. There is no particular settings to be tune. All the caching/building should work out of the box. The only things that would cause the DDC to pop again would be if the data got invalidated (e.g.: some properties of the groom asset changed or some properties of underlying skeletal mesh asset changed).

Does it happen all the time? If you start the editor several time in a row, does it happen every time?

/Charles.

[Attachment Removed]