I have a parent blueprint that I created a float variable in (set the value to 50), then set that variable to be editable and made a child blueprint. I edited that variable on the child to be (30) and everything worked fine in version 4.5 When the project was converted over to 4.7 all of my variables in the children blueprints have been wiped out or set to zero. This not only happened on floats but also class variables were cleared out. This also happened in all of my child blueprints’s even ones with other parents.
I tried a few different things, on the variable in the child bp I have clicked the yellow arrow to reset the value to the default, compiled and saved the blueprint. But when I close and reopen the editor it wipes out all of my values again back to “0”. I know you no longer need to set the editable flag to expose the variable so I also tried unchecking this, compiling the master, saved, compile the child, edited the child value, saved and re-opened but with the same results. My variable is not set anywhere in the construction script (I’ve seen some other people with this issue)
(One note is that this content was made in 4.5 and converted over to 4.7 however I have also created a new variable in 4.7 and I get the same results)
Your bug report is spot on - this was fixed in this commit. Unfortunately it won’t be fixed in the binary releases until 4.7.3.
Thanks for taking the time to report the issue - your post is very clear and I think it might help other people figure out what’s going on until we get the hotfix out. As far as I can tell there should be no data loss, so you should not have to reconvert your project once the hotfix is released.
I don’t have an exact date for 4.7.3 - we are trying to be very selective with changes, but also want to get as many fixes in as possible and we want to test it well. 1 week is my conservative estimate.