I’m wondering what the expected behavior is if I add an actor with an component and running coroutines to the Seamless Travel Actor list (the list of actors to remain alive when switching to a new level). It seems like reinitializes when a new level is loaded, so I’m wondering if there may be issues during the transition.
Do you have a preferred behavior?
Perhaps we can make it fit your needs.
Ideally it would just pause all coroutines and unpause when the level is brought up (or just not tick them, is there a difference?).
When the new level loads, the actor would not have its constructor called nor would it receive a BeginPlay event. This would mirror how existing actors are treated during seamless travel.
This should be doable and makes sense.
We’ll double check the current behavior - though it probably does reset with a new level as you have observed.
Consider it on our to do list.
How critical a feature is it for you? Are you being gated by it?
I was just considering its implementation, so it’s not critical at all. More of a theoretical/something I might consider later on.
We are focusing on the new IDE and GDC, though this is good to know about.