Editing a BP with a Spline component deletes all splines in the level

I made a BP with a spline component. then I made 2 of these in the level. Then I made/edited the spline lines in the level with those 2. Then I edited my BP, added another component and added something to the event graph. Now after compiling, the splines I made in the level are gone, reset to the default straight spline line.

Is this bug?
Otherwise is there a way to keep it from resetting the splines in the level on recompile of the Blueprint?

Hi Davision,

I wasn’t able to reproduce this behavior in-house, the splines keep their changes in the editor. What component type did you add and what exactly did you add to the Event Graph? Please include screenshots if possible.

Hi Davision,

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 the additional information I requested above.

Cheers,

TJ

Yea, it isn’t as frequent as it first appeared. I had it only happen 2 times more but couldn’t nail it down to anything.

I basically I recreated the “movement along a spline” of the splines example and made lots of instances of it with lots of different splines. It is a hidden cone mesh with capsule collision attached to that that moves along the spline. The root of the BP is not the spline and instead DefaultSceneRoot.

When it happens again and I can see what caused it I will let you know here.

Sounds good. Just post back here and it will reopen the report.

Was this ever fixed? I ran into this today in 4.12.5

Recompiling the Blueprint deleted all the spline component data. IE: All the point locations. :frowning:

Seems like there’s some issue with recompiling BPs with spline components in them.

Hi ook,

We couldn’t pin down a repro of the issue internally.

If you have more info, please feel free to post it. Any sort of repro steps would help; or even upload a small test project if possible.

This just happened to me in 4.18.
And I couldn’t recreate the bug! Gah!