# Long Hang Time When First Creating Modular Control Rig 

**URL:** <https://forums.unrealengine.com/t/long-hang-time-when-first-creating-modular-control-rig/2856615>\
**Category:** Programming & Scripting\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [October 16, 2026, 11:49am UTC](https://forums.unrealengine.com/t/long-hang-time-when-first-creating-modular-control-rig/2856615 "2026-10-16T11:49:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 16, 2026, 11:49am UTC](https://forums.unrealengine.com/t/long-hang-time-when-first-creating-modular-control-rig/2856615/1 "2026-10-16T11:49:33Z")

</div>

- **The first time a Modular Rig is assigned to a Skeletal Mesh in the Sequencer within an Editor session the engine gets stuck and hangs for almost a minute before the Modular Rig is finally assigned.**

The second time the Modular rig is assigned there is no lag or hanging time.

This also happens when first opening a Sequence containing a Modular Control Rig. It seems indeed that it happens when the Editor has to first create the rig and then it relies on cached information to re-created the following times.

Once created, the rig performance seems to be as smooth as a normal Control Rig but the initial hang time is worrying.

The more modules contained in the Modular Rig the longer the hang time.

We precise that we have created the Modular Rig by following the logic of our Control Rig overall so the graph itself should have similar evaluation times.

We are concerned that when there are many different Modular Rigs used within one project this hanging time will become unacceptably long. Is there any way we can ameliorate the issue? E.g. are there any gotchas when creating the Modules to improve this hangtime? Is this an issue that has already been flagged and will be fixed soon?

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 16, 2026, 11:49am UTC](https://forums.unrealengine.com/t/long-hang-time-when-first-creating-modular-control-rig/2856615/2 "2026-10-16T11:49:36Z")

</div>

**Steps to Reproduce**  
We tested multiple scenarios to make sure it was not our set up which was failing:

1.session of Unreal

Spawn MCR\_Quin\_Simple NON-LAYERED: 18 sec

Span MCR\_ManViz\_puppet\_default NON-LAYERED: 18 sec

2.session of Unreal

Span MCR\_ManViz\_puppet\_default NON-LAYERED: 18 sec

Spawn MCR\_Quin\_Simple NON-LAYERED: 18 sec

3 session of Unreal

Span MCR\_ManViz\_puppet\_default LAYERED: 78 sec

Spawn MCR\_Quin\_Simple LAYERED: 18 sec hang but failed to spawn

LogTemp: Error: Cannot add an additive control rig which does not contain a backwards solve event

To have MCR\_Quin as Layered needs to be spawn as Non-Layered and then converted to Layered. This will happen fast.If you spawn MCR\_ManViz as a non Layered rig and then convert it to layered this will also be fast (20 sec upon creation, instant conversion)

---

<div class="post-metadata">

**Author:** ![DDeVoe](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ddevoe/32/1000886_2.png) [@DDeVoe](https://forums.unrealengine.com/u/DDeVoe)\
**Post date:** [October 17, 2026, 5:48am UTC](https://forums.unrealengine.com/t/long-hang-time-when-first-creating-modular-control-rig/2856615/3 "2026-10-17T05:48:44Z")

</div>

Hey there,

We haven’t seen or heard of this; there are some rudimentary possible cases that could cause this, though:

- Synchronous asset loads of each module in the modular rig when loading.
- Extensive construction events that stack up per module. If your rig hierarchy is extensive, each module will create it each time and then the construction script would be doubly important.
- Potentially the RigVM need to compile or initialize.

All of these things can be mitigated with structural changes, but there isn’t a code fix for them (assuming there isn’t a bug). To validate, I would need a utrace with StatNamedEvents on. You can capture an insights trace in the editor. While we review the trace, you could preload the modular rig assets by opening them, then open your sequence to see if things improve. If it does, you could move to preloading those assets at editor load time, but that moves things to a different point.

“LogTemp: Error: Cannot add an additive control rig which does not contain a backwards solve event”

This indicates a module or rig is being layered, without a backwards solve, this can cause issues as well. In this case though, I currently feel this is not related.

Dustin

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 29, 2026, 9:08am UTC](https://forums.unrealengine.com/t/long-hang-time-when-first-creating-modular-control-rig/2856615/4 "2026-10-29T09:08:54Z")

</div>

Thanks for coming back to us. After further investigation, the culprit seemed to be array management in the construction script for some modules.

Setting the array length at the beginning, rather than dynamically adding elements within loops, reduced the hanging time from 1 min to 10 seconds. Another culprit was the evaluation of splines of 0 length, which we made sure to avoid.

We are safe to close this issue.

Thank you.

Sergio
