I’m about 75% through the tank course and have been experiencing major issues with blueprint values resetting after compilation. Very specifically the tank blueprint’s child components that are all subclassed. Every time I recompile, I will see random components having their values reset. Assigned meshes disappear, the projectile blueprint reference on the aiming component seems to be particularly affected, although I have probably lost 3+ hours cumulatively to re-assigning the tank track meshes and re-connecting the events. I’ve even had some of the references break completely resulting in phantom components attached to the blueprint hierarchy that are both not editable, and crash the editor when I try to rename them.
I’ve been through a number of boards and bug posts trying everything from closing the editor and compiling in visual studio to completely rebuilding the game from scratch to see if there was something corrupted.
A few things I have noticed from my experience
-
It’s not hotreload, even if I close the editor, clean the project and rebuild from scratch I experience the same issue
-
It appears to be blueprint related, as I will have the aiming component reset on the mortar blueprint while it retains it’s values on the tank blueprint or vice versa
-
I have not seen it happen to components that are not a custom subclass
-
it’s not always consistent, sometimes re-adding the component will make the issue go away for a period of time
-
It seems to happen more frequently when I am touching files related to the component that is being reset.
-
I thought it may be an issue with forward declaration and hotreload not finding the class as I was seeing a “class not found, assuming new” log message. I removed the forward declarations and saw the log message change to something akin to “successfully re-instanced X class” but the component was still reset
I’m at a point now where I am going to attempt to downgrade to 4.19.2 (and possibly rebuild the project from scratch again) as the issue is an unbearable timesink. Has anybody else experienced this issue? If so, maybe we should be warning people away from using 4.21.