Variables reset on packaging, sometimes when reopening map

Created a new actor BP with a skeletal mesh and a few static meshes, set it up the way I liked. Exposed some variables to change various options at runtime, like rotation or animation type etc. Works fine in the editor. I have some stuff in the construction script, nothing that modifies toggled variables though.

Package the game. All variables default. So the 40 instances of the actor, each with unique behavior all revert to defaults. Reset it tried again, same result. Created more specific child actors with fewer options. Drag the actor into the map, set the various settings. Again, works fine in the editor while the map is open. Packaging reverts them all back to defaults. Maybe the default of the parent and not the child even.

One time I opened a new map while in the editor, then went back and they’d reverted. I’ve wasted two days resetting this map a bunch of times and rewriting the actor 6 different ways now and clearly I can’t get anywhere unless I make 40 unique BP’s all with the same code but with different defaults. Seems highly inefficient.

Yep… they are all reverting to the parents defaults.

Hello thankstipscom,

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 list of steps to reproduce this issue on our end?
  3. Could you provide screen shots of any settings/blueprints that may be involved with this issue?

I dont have time for 1 and 2 at the moment.
I confirmed the issue is definitely related to the construction script though.

I have a shooting gallery type level with targets in it. When you overlap a point x amount of targets will swing out and when you shoot them they swing back on a timeline.

Some slide back and forth, or up and down etc.

I created one actor with a bunch of settings, like check mark this bool true if you want the target to swing out left otherwise its right. Another for 180 or 90… etc

So I position the actor in the level and set my settings. Simulate. It swings out as I expect. After packaging the game they all revert to the default settings. However gameplay tags on each are intact (I use tags to determine which swing out when)

What i just tried:

I copied all the stuff from the construction script and pasted it into a macro.
I set up the target how i want it to operate (using the construction script so it updates as i toggle things). When I have it operating how I want I disconnect the construction script and obv in the editor it looks all mangled, but the macro runs at begin play and it functions as it should. I just tried the first few and built the game to test. They didn’t revert…(well they reverted and then the begin play macro setting the vars again would have “un-reverted” it)

Here’s the construction script: I circled the only vars touched in the CS

And here is what I’ve had to add to the parent at startup so that after the vars get set to defaults it resets them to my specified values at run time.

So at run time it first runs the SetStartupVariables macro and then runs another macro which contains what was normally in the construction script.

I’ll try a fresh project later when I have some free time. This project is very large and was upgraded recently from an older version. However THIS actor and map were all created fresh just last week on 4.15

Well its not the construction script. It’s still happening even by setting the variables on begin play.

I just cant set the settings I want in the details panel while an actor is in the level and have it persist past a restart of the editor or a package of the game, it always reverts back to defaults of the parent. Makes building puzzles with recurring actor types impossible.

This is 100% a bug. After searching around it looks like its identical to the post here but still not fixed?: There are repro steps in there and even some projects were posted but I don’t see much in the way of a response as to a fix…

I tried the “fix” where someone mentioned putting the parent BP into the level somewhere. No idea why that might work. But I did it… and the child bps retained their settings after build…at least once so far.

Hello thankstipscom,

I am happy to hear that you have found a workaround for your issue. Thank you for the additional information you have provided above. However, I have been unable to reproduce this on my end so far. Please be sure to update the thread when you are able to reproduce this issue in a clean project so that I can investigate further.

Hello thankstipscom,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.

Thanks,