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
7000.0.0a1
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
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.