Tbh this action is quite useless/inefficient to someone who knows how to code custom actions...but may help some FSMs in dealing with objects currently updating in fixed or late update (like controllers or cameras).
I personally have had to use this for calculating velocity movement of a transform that was moving in fixed update. When I used the normal next frame event action to loop back to the calculations, my results were not consistent. I ended up making a fixed update next frame action and it was solid...but ended up making a custom action for velocity movement anyways. Might help some people though so thought ide share.
