This bug appeared in 4.11 (in 4.10 it works).
When adding Child Actor Component in Construction Script in ‘A’ blueprint and calling any function/changing variable from this child, it won’t fire after editor restart. After recompiling the ‘A’ blueprint, it goes back to normal.
… So it’s not only about functions, but everything!
2 - Even just moving the actor after restart (or forcing it to execute Construction Script in another way) causes proper child actor behavior, without need to recompile it (which unfortunately can’t be used for workaround) So the bug occurs only right after editor restart.
I am also having this issue. Additionally - after upgrading to 4.11 - The forest maker does not work with multiple landscapes. It is not placing trees to the nearest landscape below the blueprint actor. It’s placing them on the landscape below the landscape.
Thanks for reporting in! I really hope that they will fix it for 4.11.1
Regarding ForestMaker issue, please contact me on contact@unknown-origins.com and I’ll help you from there. For the start, try to move your ForestMaker actor in editor or change something in its properties. In my 4.11 project, it spawns trees correctly, always at the first detected surface below.
Seems like more people are affected by this bug, here’s another example demonstrating this issue by user @BPANDREW : https://www…com/watch?v=4jfW_fLHTg0
+ Important note: This bug occurs not only after editor restart, but after every map load.
Thank you for the compact repro case. I’ve identified the cause and submitted the fix to the Release branch for hotfix 4.11.2. If you are building your own engine code the fix is simple to apply and you could pull the fix from github now:
i still have this issue randomly happen - its not longer a show stopper for me… but I think theres still something to be sorted out - maybe its fixed in 4.12?