Search Issue Tracker
Fixed in 2023.2.13f1
Fixed in 2023.2.X, 2023.3.X, 7000.0.0a1, future release
Votes
0
Found in
2023.1.4f1
2023.2.0a23
2023.3.0a1
Issue ID
UUM-44012
Regression
No
The first frame is not affected when using the Awaitable.NextFrameAsync method
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Observe the Console Window
Expected result: “Started frame 20” message is followed by “Frame 21” message
Actual result: “Started frame 20” message is followed by “Frame 20” message
Reproducible with: 2023.1.4f1, 2023.2.0a23
Could not test with: 2021.3.28f1, 2022.3.5f1 (Awaitable class is not available for these versions)
Reproducible on: Intel macOS 13.4
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
kdchabuk
Aug 14, 2023 20:26
"actual result" and "expected result" are reversed in the description.