Search Issue Tracker
Fixed
Fixed in 2023.3.X, 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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment