Search Issue Tracker
In Progress
In Progress in 2020.3.X
Fixed in 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
- Element UI disappears and NullReferenceException is thrown when dragging off the last or first element from the list in the Inspector
- [Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode
- [Android] GraphicsBuffer.CopyCount does not work with Append Compute Buffer after Compute Shader Dispatch on some Android devices
- "DirectoryNotFoundException" error when building a project via script in one folder, then building via Editor in another, deleting the folder built via Editor and rebuilding via Script
- New items are created and old ones remain in memory when using 'treeView.SetRootItems(items)' and 'treeView.Rebuild()' which can cause a memory leak
Resolution Note (2022.1.X):
Backport to branch 2022.1 has stopped as it reached end of life.