Component Hierarchy not consistent between BP class and instance (SplineMesh not parenting properly)

Development Programming & Scripting
21

Using that approach the splineMesh is now not parented to the spline in the blueprint either…

22

It seems to parent fine if it’s right at the root, but if it is in another step then it (the spline mesh) won’t.

23

I am attaching a new file to my question, showing my code and the new hierarchy, it will be called newCodeHierarchy.jpg.

24

Ah, that’s what we were doing differently. I was only adding two components, as in your previous question you stated it didn’t matter what the spline mesh was parented to.

What it looks like is, as you said, if it is another step in from the root component, the spline mesh will have issues maintaining the correct hierarchy.

I’m going to spend some time looking into this issue and I’ll get back to you as soon as I have additional information.

25

Apparently the issue was that the SplineMesh was static by default (odd that this wasn’t an issue in 4.10) and therefore cannot be parented to a movable component (like the Spline). I solved this by setting the mobility of the component in C++ before attaching it using SetMobility(EComponentMobility::Movable). Now the SplineMesh is parented correctly in the blueprint as well as the instance of the blueprint.

Thanks for your help debugging, Sean!