Search Issue Tracker
Fixed in 2020.3.46f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a17
Won't Fix in 2022.1.X
Votes
0
Found in
2020.3.37f1
2021.3.6f1
2022.1.10f1
2022.2.0b2
2023.1.0a4
Issue ID
UUM-11450
Regression
No
Editor can not determine if GraphicsFence has passed when using CommandBuffer
Reproduction steps:
- Open the attached project(CommandBufferBug.zip)
- Select Assets/Scenes/POC
- Enter Play Mode
- Observe the error in the console window
Expected results: Editor shows if GraphicsFence has passed
Actual results: Editor could not determine if GraphicsFence has passed
Reproducible with: 2020.3.37f1, 2021.3.6f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4
Reproducible on: Windows 11
Note: The workaround would be to use Graphics instead of CommandBuffer which should do the same thing according to documentation
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
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
Resolution Note (2022.1.X):
Backport to branch 2022.1 has stopped as it reached end of life.