Why do default values in a child blueprint get overriden by the default in the parent blueprint?
Sometimes the default value in the parent overrides the default value set in the child blueprint. There does not seem to be a rhyme or reason to what sort of variables this can happen to, I have specifically seen it with the AiControllerClass variable (in pawn) as well as UseControllerRotationYaw (again in pawn) as well as rotation (in the transform of a mesh attached to a character) as well as a slew of blueprint created variables.
My solution thusfar has been to set the value of a variable to what I actually intend it to be in the construction script of effected blueprints. I do hope this issue is resolved before the construction scripts get larger than the actual blueprint code in my classes.
It may be the same problem described here: https://answers.unrealengine.com/questions/144063/defaults-resetting-on-bps-derived-from-other-bps.html
asked Mar 21 '15 at 09:09 AM in Bug Reports
Good Morning. Is this problem open yet right?.
I have the same problem, I created a blueprint with some variables (editable), I create the child blueprint class, when I add the child in an scene I can changed the variable without any problem, but If I duplicate the actor in the scene, the new object return to default value, don't keeping the variable of he child that I duplicated.
I'm using unreal 4.15
After doing some digging I was able to find that this issue was reproduced and a report has been written up. I have provided a link to the public tracker. Please feel free to use the link provided for future updates. I have also provided a link to another thread with more information on this issue.
Link Public tracker: https://jira.it.epicgames.net/browse/UE-18765
Make it a great day
answered Jun 30 '17 at 01:55 PM
Rudy Q ♦♦ STAFF
I still have this error in 4.14. If I inherit Editable Variables from Parent. They always return to their status as the default has been described here: https://answers.unrealengine.com/questions/330290/bug-wprojectfiles-default-value-of-blueprint-reset.html
answered Dec 07 '16 at 10:16 AM
We are working on 4.13 and are experiencing the same issue where blueprint children and instances of these (npc characters in our case) placed in the world will loose all there custom variables (BP editable variables will be set to parent defaults). So far I have only seen this after a startup of the editor.
answered Mar 20 '17 at 03:26 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here