Waiting for a coroutine in a coroutine takes 1-Tick for the process to return about ue5coro HOT 5 CLOSED

Remarks:
Since LatentActionManager is processed in the order of registration, the problem seems to be caused by the fact that the resumption process of the external coroutine is not called until the next frame after the internal coroutine has finished.

WhenAll, WhenAny, etc. were registered and processed after the internal coroutine, so they behaved as intended.

from ue5coro.

This behavior is by design and documented. Latent coroutines are fundamentally owned and controlled by the latent action manager and can only complete when it processes them on its own tick. This matches BP and most existing Latent UFUNCTIONs from the engine, which is the primary focus of this mode of execution.

In some situations that I encountered, I managed to skip the extra tick by returning an inner TCoroutine instead of co_awaiting it.

from ue5coro.

Thank you for your response,
Sorry for the inconvenience,

In some situations that I encountered, I managed to skip the extra tick by returning an inner TCoroutine instead of co_awaiting it.

If you don't mind, I would appreciate it if you could tell me what exactly you did in response.

from ue5coro.

@aziogroup Instead of

TCoroutine<> Fn1();
TCoroutine<> Fn2()
{
    DoStuff();
    co_await Fn1();
}

it's

TCoroutine<> Fn1();
TCoroutine<> Fn2()
{
    DoStuff();
    return Fn1();
}

from ue5coro.

Thank you very much!
It seemed difficult to apply it to my case, but in a simple case this seemed to be the way to get around it.

from ue5coro.