Search Issue Tracker
Fixed
Fixed in 2020.3.46f1, 2021.3.17f1, 2022.2.3f1, 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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2022.1.X):
Backport to branch 2022.1 has stopped as it reached end of life.