Search Issue Tracker
Fixed in 2021.3.34f1
Fixed in 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a14
Votes
0
Found in
2021.3.30f1
2022.3.8f1
2023.1.11f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-47689
Regression
No
"NotSupportedException: Cannot determine if this GraphicsFence has passed as this platform has not implemented GraphicsFences." is thrown when using GraphicsFence
How to reproduce:
1. Open the attached project "Shaders debug.zip"
2. Enter Play Mode
Expected results: No errors thrown in the Console window
Actual results: "NotSupportedException: Cannot determine if this GraphicsFence has passed as this platform has not implemented GraphicsFences." is thrown
Reproducible with: 2021.3.30f1, 2022.3.8f1, 2023.1.11f1, 2023.2.0b7, 2023.3.0a3
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment