ChildActor of my pawn keeps getting duplicated and orphaned.
I posted this originally here in the Blueprint Scripting section, but after getting a confirmation from another user that their child actors were behaving similarly and only in 4.17 I thought I'd post it here for better visibility.
Ever since I moved to 4.17 I've been noticing a reoccurring issue in my project. I have a blueprint named "bs_PathMark" which is really quite simple, just a looping timeline of an arrow going some distance which more or less acts as a pointer and "power" meter, which is assigned to a ChildActor on my player pawn.
Prior to 4.17 everything worked perfectly. But since moving to 4.17 I started noticing duplicates of this "bs_PathMark" in the level and in the world outliner. These duplicates are left at the players beginning location. The orphaned actor's timeline reflects the playrate being set on the player (which implies its getting updated blueprint information from the player, how I'm still unsure) but they aren't attached to the player nor do they rotate with the player. I've noticed in world outliner as many as half a dozen. I keep deleting them (without issue) and they keep reappearing.
I've looked for an explanation but have yet to uncover one. I am not "spawning" this actor nor am I assigning this class to the ChildActor at run time. These are all values set in the player pawn, so how its generating more than one I am at a loss. Since they only appear at the player's beginning location I suspicious of some bad initialization or some bug introduced recently but I'm currently at a loss.
I've placed some print strings at BeginPlay to let me know when they're appearing but that wasn't really much help. If I delete the extras, I could get new duplicates in a few sessions in PIE or in a dozen which makes it very frustrating to hunt down. Is there some logic I could stuff in the class to find out what is absolutely calling it? Or what is spawning it?
I've attached the entirety of the blueprint in question in the attached image. It's not very big.
asked Sep 06 '17 at 06:34 AM in Bug Reports
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.
answered Sep 27 '17 at 06:09 PM
Thomas G ♦♦ STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here