Select component in blueprint while running is crash

Development Programming & Scripting Blueprint
, , ,
1
  • I run from editor (simulate mode).
  • Eject
  • Click custom blueprint that contains nested components
  • Select a child component → crash → see pic…

30467-select_bp_is_crash_lol.png
30467-select_bp_is_crash_lol.png3836×1080 586 KB

Edit:
I noted that it occurs when a blueprint has at least an InputComponent (Which shows up Green in the components on the right in the details panel when running (SimulateMode)).
Then, when you select the horizontal separator bar to enlarge the components detail panel (drag it up and down). It will crash almost immediately.

2

Hey simmania-

Does this break occur when not running the game through Visual Studio? Also, could you post the log files for the project from when the crash happened. Additionally, what is the blueprint you’re using based on (Actor, PlayerController, etc.) and which components are you using other than the InputComponent? Are you setting up the components through code or in the component tab of the blueprint?

Cheers

3

Hi ,

It does not happen when starting without VS.
However, there is nothing special going on.
The crash is easy to reproduce.

  1. Start a new project with minimal content such that a Sky and Fog are created (which is almost always the case).
  2. Start in simulation mode.
  3. Select BP_Sky_Sphere
  4. Go to details panel (default on right).
  5. Grab the horizontal seperator bar such that the InputComponent_1 (Green) becomes visible and move it a bit up/down.
  6. Some tooltip is about to get shown according to code in VS and this is where the bug occurs.
  7. It checks/ensures that the InputComponent is created in a ConstructorScript which is apparently not the case.

This occurs in 4.7.0.p7

4

Where are you adding in the InputComponet_1? I do not see it in the Details panel when I have the BP_Sky_Sphere selected. Additionally, if this breakpoint only occurs when running through the Visual Studio debug mode it shouldn’t affect your project since the Editor can work through it on its own.

5

Set AutoReceiveInput from Disabled to Player0.
Then run in Simulate mode.
An InputComponent will be automatically created.
Drag de horizontal seperator bar up down to get the (Green) Input component visible is crash in VS.
Maybe the editor can work through it, but there is no way of continuing in VS when a breakpoint is hit.
So i have to test without VS started but that makes no sense since I am doing most of the stuff in C++

6

Hey simmania-

I was able to reproduce the breakpoint you described and have entered it into our internal tracking database (UE-10684) for further investigation. The InputComponent seems to be auto-generated when “Auto-Receive Input” is set to something other than default. As a workaround you can set “Enable Input” on a Begin Overlap Event and Disable Input on an End Overlap Event instead.