Clicking on a static mesh in BP crashes editor

Michael_Boeni · May 23, 2014, 3:06pm

I can reliably (every time, in multiple blueprints) crash the editor when I click on a static mesh in the BP component editor (viewport). When I select the component in the outliner of the BP editor, it works fine.

Also: Selecting instanced geometry in the BP component editor does NOT crash the editor.

I already sent over several crash reports.

Cheers,
Michael

_Epic_Ori_Cohen · May 23, 2014, 5:17pm

It sounds like a problem with the raycast on the BSP.
Would you mind linking the crash report or pasting the callstack?

Thanks

Michael_Boeni · May 23, 2014, 9:26pm

Here you go:

We apologize for the inconvenience.
Please send this crash report to help improve our software.

36bf66a154db6e1d91a889f7a9732a49

Michael_Boeni · May 23, 2014, 9:27pm

By the way, I am having the issue with static meshes, I haven’t tested BSP brushes…

_Epic_Ori_Cohen · May 23, 2014, 10:41pm

Hey sorry I misread BP as BSP.
Could you post the full report? I only see the top 3 lines.

Thanks

Michael_Boeni · May 23, 2014, 11:23pm

That’s all i got from the crash reporter. Is there any other place I can find information on the crash?

Stephen_Ellis · May 28, 2014, 5:41pm

Hi IMX,

Sorry for the confusion, you did correctly share all that the CrashReporter has to offer. The long string is an ID that we use internally to track down the crash information submitted by the CrashReporter.

However, for some reason, we don’t have anything turning up for the ID that you gave. Would you mind crashing again, submitting the report, and giving us the new ID?

Also, in case that ends up failing again, please go ahead and (after a fresh crash) submit your latest log found here:

C:\Program Files\Unreal Engine\4.1\Engine\Programs\CrashReportClient\Saved\Logs

Thanks!

Michael_Boeni · May 28, 2014, 6:15pm

Hi Stephen

No worries I just provoked another crash and here is the string:

36bf66a154db6e1d91a889f7a9732a49

Cheers,
Michael

link text

anonymous_user_bcdd396d · October 3, 2014, 7:08pm

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.

If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.

Thank you.