Search Issue Tracker
Fixed
Fixed in 2022.3.47f1, 6000.0.20f1
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.41f1
2022.3.40f1
6000.0.13f1
Issue ID
UUM-77339
Regression
No
Vector and Vector<T> do not receive hardware acceleration
Reproduction steps:
1. Open the attached “VectorIntrinsicBug” project
2. Observe the Console logs
Expected Result: “Vector.IsHardwareAccelerated: True” is shown
Actual Result: “Vector.IsHardwareAccelerated: False” is shown
Reproducible with: 2021.3.41f1, 2022.3.40f1, 6000.0.13f1
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
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
- 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
Resolution Note:
This issue is specific to the mono scripting backend which is not available in this release.
Resolution Note (fix version 6000.0.20f1):
Fix issue where Vector and Vector do not receive hardware acceleration.
Resolution Note (fix version 2022.3.47f1):
Fix issue where Vector and Vector do not receive hardware acceleration.
Resolution Note (2021.3.X):
This is currently too risky to bring back to 2021.3 and we don't want to introduce regressions into a mature stable release.