-
-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WaitForFixedUpdate does not work as described #377
Comments
Thank you very much. |
Please. I just came across a similar issue where a bug was introduced because I expected the behaviour to be the same. |
neuecc
added a commit
that referenced
this issue
Oct 24, 2022
released at 2.3.2. |
pillsgood
pushed a commit
to pillsgood/UniTask
that referenced
this issue
May 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This line from documentation is wrong:
Coroutine WaitForFixedUpdate is called the same frame after physics update and when used in OnTirggerXYZ family callbacks it will correctly be called the same frame after callbacks. Unitask behaviour is different - it will be called next frame and probably at the beggining of FixedUpdate. To get the same behaviour I needed to use
UniTask.Yield(PlayerLoopTiming.LastFixedUpdate);
The text was updated successfully, but these errors were encountered: