# Merge Actors doesn't work with Instanced Static Meshes

**URL:** <https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356>\
**Category:** Asset Creation\
**Tags:** actors, merge, unreal-engine, instances, question\
**Created:** [January 30, 2017, 12:55am UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356 "2017-01-30T00:55:13Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Slavq](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Slavq](https://forums.unrealengine.com/u/Slavq)\
**Post date:** [January 30, 2017, 12:55am UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/1 "2017-01-30T00:55:13Z")

</div>

This seems very basic, repro:

1. Create a blueprint that generates some random instances, e.g. like this:

[![](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/5/e/95ec9e29bdf7cc72e6c25c2300f5155fc749954e.png) ](https://i.imgur.com/Logdxdl.png)

1. Place it in a scene and try to merge it via Merge Actors

Result: When merging into static mesh, it will ignore any instances and place them at 0,0,0.

Similar report, but from 4.12, can be found [here.][2]

---

<div class="post-metadata">

**Author:** ![S-ed](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/s-ed/32/1194558_2.png) [@S-ed](https://forums.unrealengine.com/u/S-ed)\
**Post date:** [January 30, 2017, 3:53am UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/2 "2017-01-30T03:53:43Z")

</div>

There was one more thread on this topic:

> **[Merge Actors: 2 bugs](https://forums.unrealengine.com/questions/357688/merge-actors-2-bugs.html)**
>
> I’ve discovered two easily reproducible bugs when using the experimental “Merge Actors” tool. First bug: It ignores any Instantiated Static Mesh Components. After merging, it leaves only one and ignores its scale. How to reproduce: 73671- Place...

And Epic claiming bug is fixed:

> **[The Unreal Engine Issues and Bug Tracker](https://issues.unrealengine.com/issue/UE-25187)**
>
> Welcome to the Unreal Engine Issue and Bug Tracker. You can check the status of an issue and search for existing bugs. See latest bug fixes too.

---

<div class="post-metadata">

**Author:** ![Slavq](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Slavq](https://forums.unrealengine.com/u/Slavq)\
**Post date:** [January 30, 2017, 11:34am UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/3 "2017-01-30T11:34:35Z")

</div>

Yes, that’s my own report 🙂 It’s for 4.12, it looks like the first bug (child actors) is fixed, but instanced meshes are still broken.

---

<div class="post-metadata">

**Author:** ![TJ\_V](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tj_v/32/1008648_2.png) [@TJ\_V](https://forums.unrealengine.com/u/TJ_V)\
**Post date:** [January 31, 2017, 9:23pm UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/4 "2017-01-31T21:23:49Z")

</div>

Hey Slavq,

Thank you for the report. I was able to reproduce this behavior and I’ve created [JIRA UE-41366](https://issues.unrealengine.com/issue/UE-41366) and our developers will be investigating further. Follow that link to monitor the status of the bug report.

As a workaround; do you need to use instanced meshes for what you are doing? You look to be using this blueprint setup to create randomized Static Meshes through the Merge Actor tool. If this is the case, you can use Add Static Mesh Components instead and this issue doesn’t occur.

I know they aren’t as performant but if you are only using this as an editor tool to create Static Meshes, then it shouldn’t be to bad unless you are creating a really large amount of components.

Cheers,

TJ

---

<div class="post-metadata">

**Author:** ![Slavq](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Slavq](https://forums.unrealengine.com/u/Slavq)\
**Post date:** [January 31, 2017, 9:43pm UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/5 "2017-01-31T21:43:52Z")

</div>

Thank you!  
Yes, this is exactly what I ended up doing as a workaround for now 🙂  
Cheers!

---

<div class="post-metadata">

**Author:** ![Cameron\_Abt](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Cameron\_Abt](https://forums.unrealengine.com/u/Cameron_Abt)\
**Post date:** [May 9, 2017, 2:39am UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/6 "2017-05-09T02:39:44Z")

</div>

Hey TJ,

Was just taking a look at the JIRA ticket and it seems that it was dispositioned as “by design.” Can you comment on why this is the designed behavior? Seems counterintuitive to me, and makes it harder for those like me who have blueprints to create final meshes but leave them in the world during design in case we want to make tweaks down the line.

Thanks!  
Cameron

---

<div class="post-metadata">

**Author:** ![TJ\_V](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tj_v/32/1008648_2.png) [@TJ\_V](https://forums.unrealengine.com/u/TJ_V)\
**Post date:** [May 15, 2017, 1:36pm UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/7 "2017-05-15T13:36:03Z")

</div>

Hey Cameron,

Sorry for the delay.

This is because the current instance static mesh components are not supported in the HLOD / merge actor system by design. However, we are working on another feature that may address this in the future.

---

<div class="post-metadata">

**Author:** ![bad.man](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@bad.man](https://forums.unrealengine.com/u/bad.man)\
**Post date:** [August 5, 2024, 7:30pm UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/8 "2024-08-05T19:30:54Z")

</div>

Was there ever an update on this? You can combine them in a PLI but it would be a lot cleaner if you could simply combine multiple ISMAs into one parent actor with multiple ISM components. I’m trying to reduce actor count with procedurally instanced meshes.

---

<div class="post-metadata">

**Author:** ![RecourseDesign](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/recoursedesign/32/1194503_2.png) [@RecourseDesign](https://forums.unrealengine.com/u/RecourseDesign)\
**Post date:** [August 5, 2024, 7:33pm UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/9 "2024-08-05T19:33:35Z")

</div>

rdInst has an “auto instancing” system which works with instances and PLAs etc, combining them into a singleton instance manager at runtime:

> **[rdInst Tutorial 40 - Recourse Design ltd.](https://recourse.nz/index.php/rdInst-tutorial-40/)**
>
> rdInst Tutorial 40 – Auto-Instancing with rdInst Last Updated: 8th June 2024Tutorial created using rdInst version 1.41 Version 1.40 of rdInst introduces a new tool which makes optimizing your levels extremely easy. The idea was suggested by RomanK...

---

<div class="post-metadata">

**Author:** ![Yabab](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Yabab](https://forums.unrealengine.com/u/Yabab)\
**Post date:** [September 26, 2025, 12:21am UTC](https://forums.unrealengine.com/t/merge-actors-doesnt-work-with-instanced-static-meshes/383356/10 "2025-09-26T00:21:37Z")

</div>

In Unreal Engine 5.3.2, the Merge Actors function works with ISM’s.

If you’re using Merge, either set the HLOD Batching Policy of the Components being merged to None or deactive the “Include Imposters” boolean before merging.

If you’re using Simplify, then you must set the HLOD Batching Policy of the Components being merged to None.

If you don’t do that, you trigger the Imposter flow, which seems to place the imposter at local 0,0,0.

For Batch or Approximate, they work out of the box.
