Editor crashes when an actor collides with a destructible blueprint

Development Programming & Scripting Blueprint
, , , , ,
1

Hello,

Thank you for your report. Could you please go into your [Project Name]/Saved/Logs folder and attach the log file to your post? That will let us further investigate the crash.

Thank you!

2

Hi,

I have been trying to implement a destructible wall which will explode on hit by an actor. Rather than do this on a per-object basis in the level blueprint I wanted to created a blueprint of a destructible wall which can handle its own logic and be able to use it in multiple locations.

To do this I took the wall static mesh from the sample content, created a destructible mesh version of it, then created a blueprint from that and dropped it in the level. On playing the game and running my character in to the blueprint version of the destructible wall the editor crashes. The blueprint contains no changes and nothing in the graph.

If i drop in just the destructible mesh without the blueprint it does not crash.

If there is any work around for now (other than doing all the scripting in the level blueprint) I’d be very greatful! :slight_smile:

EDIT: I first encountered this on build 4.0.1 so i got the latest preview build off github which the editor load screen suggests is version 4.1.0 but the issue still occurs.

3

I’ve attached 2 log files for you, one from version 4.0.1 and one from 4.1.0.

4

Has the been any update on a way to fix this?

5

hi I got same problem sith a simple box of 100x100x100 transformed in static mesh, when I try to make a destructible mesh from other asset not made by me it’s work but on my self made asset it’s not work some log crash as the one included:

[2014.04.15-18.51.07:054][882]LogDestructible:Warning: MainMesh Tris: 12

for my part it’s happen on 4.0.2 when I click on the create destructible mesh in the content broswer (in the context menu of the right click of the asset.

6

Hi,

This bug is unrealted to async scene. I’ve added this as a task and will keep you posted on the fix. Sorry for the pain

UPDATE: This issue should now be fixed. It will be in the upcoming release. If you’d like to get it from github let me know and I can provide more details

7

I experience the exact same issue, sadly.

8

Export the mesh out as an FBX then import it again - this fixes this issue.

9

Experiencing the same problem on 4.8. Regression?

10

It could be, but can you post a callstack and attach the log file so we can verify that it has come back?