Search Issue Tracker
Fixed
Fixed in 2023.3.0b5
Votes
0
Found in
2021.3.29f1
2022.3.8f1
2023.1.11f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-49593
Regression
No
”FrameData.frameId” is not consecutively incremented when manually evaluating a PlayableGraph
How to reproduce:
1. Open the user’s attached project “Repro.zip”
2. Open “Sample” Scene
3. Enter Play Mode
4. Observe the Console
Expected results: “frameId - lastFrameId = 1” is logged
Actual results: “frameId - lastFrameId = 2” is logged
Reproducible with: 2021.3.29f1, 2022.3.8f1, 2023.1.11f1, 2023.2.0b7, 2023.3.0a3
Reproducible on: macOS 13.5.2 (Intel), macOS 13.4.1 Ventura, Windows 10 22H2
Not reproducible on: No other environment tested
Notes:
- frameId is incremented by 2 for every call to “Playable.PrepareFrame”
- reproducible in the Editor and Standalone Player
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
Add comment