09-28-2021 06:45 PM
What does the "Auto-Stop" setting in "Launch Nested Actor" do? I noticed that I still had to include "Send Normal Stop" to stop the nested actor, even with the Auto-Stop setting set to TRUE. I had initially expected that it would stop as soon as the Caller Actor stopped when this setting was set to TRUE.
Solved! Go to Solution.
09-28-2021 06:57 PM - edited 09-28-2021 06:58 PM
Auto-stop should propagate your Stop message to all nested actors. It won't guarantee the nesteds do anything about it. For example, they might keep running if they ignore the Stop, or a helper loop hangs.
Also, I don't think the root/caller actor will wait for them to shutdown; it forwards the Stop, then it dies. You can override Handle Error to create this "wait" behavior yourself, if you need it.
09-29-2021 07:44 AM
I noticed that I still had to include "Send Normal Stop" to stop the nested actor, even with the Auto-Stop setting set to TRUE.
You should not have to do that... that is indeed the whole point of the autostop. What happened that made you think you needed that?
09-29-2021 08:58 AM
I think it's exactly what would happen if you forked the caller when launching the nested actor:
09-29-2021 09:11 AM
09-29-2021 11:20 AM - edited 09-29-2021 11:23 AM
Dingdingding! Give Jonzarwal a cupie doll. I had it wired as shown in the "Wrong" example. When I eliminated the fork, everything shut down as I expected. Thanks!