Search Issue Tracker
Fixed in 2020.3.48f1
Fixed in 2020.3.X, 2023.2.X, 2023.2.0a11
Votes
0
Found in
2020.3.45f1
2023.2.0a10
Issue ID
UUM-27598
Regression
No
GraphicsFence.passed is passed in a random order
I am using Graphics.CreateGraphicsFence to create a fence that should pass when the previous Graphics.Draw command is completed
How to reproduce:
1. Download and open the attached project
2. Open SampleScene.scene
3. Enter Play mode
4. Observe the Console window
Expected results: A fence created on frame N+1 can never pass before a fence created on frame N (Fences are passed in ascending numerical order)
Actual results: Fences can be passed out-of-order (Fences are not passed in ascending numerical order)
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
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
- 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
Resolution Note (fix version 2023.2):
Ensure GraphicsFence.passed reports consistent results at initialization
Resolution Note (fix version 2020.3):
Ensure GraphicsFence.passed reports consistent results at initialization