In case anyone is interested, I believe I finally got to the gist of it, essentially boils down to the TickGroupOrder
PrePhysicsticks run on my char- Latent Action ticks run my delay node (referenced as
n/ain the doc, afterPostPhysics) - rinse and repeat next frame
The following simple blueprint highlights the situation:
With all that newfound knowledge, knowing the output should be easy enough, but just in case we have some people who likes a little brain teaser, feel free to try to guess the actual output for frame 1 & 2 for both implementations.
Answer bellow
Answer in the orange blocks.
Notice how first implementation has AB in the first same frame. Doubling down on DelayUntilNextTick on the second implementation only delay the print by actually 1 frame since LatentAction ticks prior rendering the frame.
Long story short, DelayUntilNextTick doesn’t mean your latent action will be processed in the next frame. It means it’ll be processed during the next latent action tick, whatever it may be.