Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.6f1
2022.1.8f1
2022.2.0a18
2023.1.0a1
2023.2.0a1
Issue ID
UUM-3098
Regression
No
Compute shader output is wrong on Direct3DX11 Graphics API when using AMD GPUs
Reproduction steps:
1. Open the user's attached project
2. Open Test Runner window: Window > General > Test Runner
3. In the Test Runner window, click "Run All"
Expected result: None of the tests fail
Actual result: Some tests fail
Reproducible with: 2021.2.16f1, 2022.1.0b10, 2022.2.0a8
Couldn't test with: 2019.4.34f1, 2020.3.26f1 (due to dependencies, downgrade errors)
Notes:
-Issue reproduces only when using Direct3DX11 Graphics API with AMD graphics cards
-Reproduced on these GPUs: AMD Radeon RX6800, AMD Radeon Pro WX 9100
-Not reproducible on NVidia RTX 2060 GPU.
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
A bug should be filed against AMD. As a rule of thumb we don't do driver workarounds in desktop platforms with updateable drivers.