# Crash converting 4.7.6 to 4.8 Destructible Component in BP

**URL:** <https://forums.unrealengine.com/t/crash-converting-4-7-6-to-4-8-destructible-component-in-bp/320512>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, bug-report, question\
**Created:** [June 2, 2015, 4:18pm UTC](https://forums.unrealengine.com/t/crash-converting-4-7-6-to-4-8-destructible-component-in-bp/320512 "2015-06-02T16:18:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![popawheelie](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@popawheelie](https://forums.unrealengine.com/u/popawheelie)\
**Post date:** [June 2, 2015, 4:18pm UTC](https://forums.unrealengine.com/t/crash-converting-4-7-6-to-4-8-destructible-component-in-bp/320512/1 "2015-06-02T16:18:22Z")

</div>

Hello, I am in the process of testing some of 4.8 features. Once my 4.7.6 scene is converted, the 4.8 editor loads and crashes.

Top line reads;

UE4Editor\_Engine!UDestructibleComponent::SetMaterial() [d:\buildfarm\buildmachine\_++depot+ue4-releases+4.8\engine\source\runtime\engine\private\components\destructiblecomponent.cpp:1402]

I opened a fresh 4.8 scene and migrated some blueprints from the 4.7.6 scene. I noticed that there is a problem (recreating the crash) with some blueprints that referenced a Destructible component. The blueprints are construction scripts, used for level design and variation, nothing complicated. Although there where some BP with destructible components working fine in 4.8.

Any Ideas to the problem or help would be greatly appreciated.

link text

---

<div class="post-metadata">

**Author:** ![popawheelie](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@popawheelie](https://forums.unrealengine.com/u/popawheelie)\
**Post date:** [June 3, 2015, 5:36am UTC](https://forums.unrealengine.com/t/crash-converting-4-7-6-to-4-8-destructible-component-in-bp/320512/2 "2015-06-03T05:36:34Z")

</div>

It seems that in a macro, add material works for a destructible if it is the node after the set destructible node, but not later in the chain… (weird). Set material for a destructible works if added after a macro. (BP\_works\_2) It will crash if the set material node is added after a set destructible mesh within the construction script.

Ok, it seems if I make a new destructible component for the 4.7.6 blueprints in 4.8 it compiles and works, that is after I disconnect any ‘set material’ nodes before migrating across.

---

<div class="post-metadata">

**Author:** ![Tim\_Hobson](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Tim\_Hobson](https://forums.unrealengine.com/u/Tim_Hobson)\
**Post date:** [June 3, 2015, 3:34pm UTC](https://forums.unrealengine.com/t/crash-converting-4-7-6-to-4-8-destructible-component-in-bp/320512/3 "2015-06-03T15:34:58Z")

</div>

Hi Popawheelie,

Thank you for the report, I was able to reproduce this and have submitted ticket UE-16522 for this to be investigated.

Once there is a fix or any update I’ll post back here.

Thank you!

Tim

---

<div class="post-metadata">

**Author:** ![popawheelie](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@popawheelie](https://forums.unrealengine.com/u/popawheelie)\
**Post date:** [June 11, 2015, 9:35am UTC](https://forums.unrealengine.com/t/crash-converting-4-7-6-to-4-8-destructible-component-in-bp/320512/4 "2015-06-11T09:35:01Z")

</div>

Cheers thanks Tim.

---

<div class="post-metadata">

**Author:** ![Tim\_Hobson](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Tim\_Hobson](https://forums.unrealengine.com/u/Tim_Hobson)\
**Post date:** [July 6, 2015, 3:09pm UTC](https://forums.unrealengine.com/t/crash-converting-4-7-6-to-4-8-destructible-component-in-bp/320512/5 "2015-07-06T15:09:59Z")

</div>

I wanted to update that this has been fixed in our internal build of 4.9.

Thank you for taking the time to report the issue. 🙂
