Question Will an awoken trigger2d collide with anything in it on the same frame it wakes?

And then if I use LateUpdate() to turn to trigger off, will this approach guarantee that all collisions have occurred with the trigger first?

I need to have a trigger turn on, collide with whatever is in it, and turn off afterwards.
But I need to make sure it doesn’t turn off too soon or in future frames.

 

Does using WaitForFixedUpdate to call a LateFixedUpdate() function work?
https://james-frowen.github.io/unity_tips/latefixedupdate/

If this works then it would ensure all my collisions are complete before I disable the collider.

 

I have a use case which involves enabling a collider, getting any immediate collision, and then disabling after.

Since there is no way to know beforehand the number of collisions, I need to just wait till the end of physics update to turn off the collider right?

Now since there is no latefixedupdate() function but there is a coroutine yield WaitForFixedUpdate, would just putting a function call there effectively call a function at the end of FixedUpdate()?

this would guarantee that any collisions that could happen have occurred first, and since I’m enabling the collider outside of the physics loop, there won’t be any weird timing thing such as where I enable collider after all triggers have happened for that physics update, and then it’s disable the collider at the end of the update, and it’d look like no collisions were there.

 

Can that be called outside of the physics loop to immediately check for overlaps, or do we still have to wait for a fixed update so the physics engine can register any overlaps for a newly enabled collider?
In which case it’d be redundant since waiting for fixed update would do ontriggerenter events anyway, so I don’t need to manually check for overlaps.

 

Ok thanks