Editor Crashes when Moving Child Object to Different folder

Development Platform & Builds
, , , , ,
1

Just as the title says.

Go to the demonstration project i have uploaded, find the object named “Focus Object” (child of LeaderLine in the StarterPoints folder) and move it to the Cameras folder (in the World Outline).

Crash! Recursion bug according to visual studio :slight_smile:

Moving to another actor doesn’t cause it though (haven’t tested extensively)

(Also, on loading the project there’s a complaint from an old C++ class which I have removed…? Just press OK)

2

Hello vikhik,

I was unable to find the assets mentioned in your post within the project provided. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so could you provide a detailed set of steps to reproduce this issue on our end?
  3. Could you provide screen shots of any blueprints that may be involved in this issue?
3

Hi Rudy, I’ll try that now. But until then, can you open the CrashDemo project I have provided and follow these steps?

54079-crashdemoinstructions1.png
54079-crashdemoinstructions1.png389×769 56.7 KB

54082-crashdemoinstructions2.png
54082-crashdemoinstructions2.png1188×735 485 KB

4

I am now able to replicate this with a blank project (4.8.3).

I am not entirely sure which of the following steps are necessary however.

  1. Open Blank BP Project
  2. Create BP derived from Actor, called BP_Line
  3. Add Static Mesh Component as a child of the DefaultSceneRoot Component
  4. Set the Mesh to be the Engine Content “Plane” Mesh
    (I also set its scale to 1.f, 8.f, 1.f)
  5. Add a BP_Line to your world
  6. Add a Target Point Actor to the world
  7. Child it to the BP_Line
  8. Add a folder
  9. Move the BP_Line to the folder
  10. ???
  11. Crash.

I have uploaded a project which has up until step 8 completed.

5

Hello vikhik,

I was able to reproduce this issue on our end. However, after doing a bit more testing I found that this issue has been resolved in the 4.9 version of the engine. Thank you for your time and information.

Make it a great day

6

I forgot to thank you for this!

Thanks!