Here is the use case:
I have a blueprints which extends Text3D actor.
I also added to this class a Text3DCharacterTransform component as I need this functionality built in.
I drop this actor into the scene, set some transform parameters on the Text3DCharacterTransform.
Add the actor to the level sequencer and mark it spawnable.
Set some keyframes which control spawn/destroy state of the actor.
Result: Each time the actor gets spawned, all the user set properties of its component are reset.
Now, I would say it makes sense since a new instance is getting created, unless I observed totally different behavior if instead of using my custom Text3D BP , I do this:
Drop into the scene a normal Text3D actor.
Add to it a Text3DCharacterTransform component via details dialog.
Tweak the props.
Same setup in the sequencer as in case with my custom Text3D BP.
And the result is that the parameters of the component do not get reset when spawned. Those are persistent!
So I would like to understand if this is an expected behavior of custom actors made with BP (if it is, this is a real bottleneck for efficient sequencer animation workflow). And if it is not, please tell me what I am missing in the setup.
Thanks.