Search Issue Tracker
In Progress
Fixed in 2023.2.13f1, 6000.0.0b11
Votes
0
Found in
2023.1.4f1
2023.2.0a23
2023.3.0a1
2024.1.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
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
kdchabuk
Aug 14, 2023 20:26
"actual result" and "expected result" are reversed in the description.