[UE 4.11] Editor crashes after changing an instance of a Blueprint

Hello Epic,

In the 4.10.2 I had a Blueprint with a simple scene component + 7 static meshes component (no scripts). I had instances of this BP on the scene. For some of those instances I duplicated up to 3 times static meshes component with no problems except with the translation / scaling / rotation / world and local space tool (particularly the scaling : X scaling scale Y or Z axis, etc).

I moved to 4.11 with no problems except one :

  1. For one of this BP instance :

  2. Duplicate one static mesh component => Record => It works.

  3. Duplicate one more SM => Record => UE4 crashes.

  4. Sometimes I had to delete the instance => UE4 crashes.

  5. Solution : delete the BP (force delete) => UE4 doesn’t crash and instance is deleted.

Temporary solution: Add 3 or more SM in the BP classes => Makes instance => Select a SM component and make it disappear if I don’t need it (by details => SM section => choose clear the SM

It’s not pretty but it works, I would prefer to delete it directly but it’s not possible).

Regards,

Hi Innuendo,

I have some additional questions.

  1. Are you duplicating the blueprint in the level or are you duplicating the components under the Details panel?

  2. When you say ‘Record’ in steps 2 and 3, do you mean Compile & save?

  3. Did you get a Crash Reporter callstack from the crash? If so, make sure to submit that and post the callstack info here.

Hello TJ Ballard,

I am duplicating the components under the Details panel and by ‘Record’ I mean Save.

And one thing I forgot to say it’s that I replaced in the BP the initial Scene Component by another Scene Component (so I can rename it as I want).

Don’t forget to answer this from above: Did you get a Crash Reporter callstack from the crash? If so, make sure to submit that and post the callstack info here.

I’m still having issues reproducing this. Could you post a test project that has this crash?

Hi innuendo,

We haven’t heard back from you in a few days, so we are marking this post as resolved for tracking purposes. If you’re still experiencing this issue, please feel free to post back here with additional information to reopen the post.

Cheers,

TJ