Search Issue Tracker
Fixed
Fixed in 2020.3.46f1
Votes
0
Found in
2020.3.41f1
Issue ID
UUM-20091
Regression
No
[Andorid] Compute Shader won't be reimported when Graphics API is changed
Reproduction steps:
- Open the user’s attached project “GraphicsAPIbug”
- Go to Player Settings (menu: Edit > Project Settings > Player)
- Select “Pc, Mac & Linux Standalone” settings
- Expand the “Other Settings” property
- Change “Graphics APIs for Windows” from “Vulkan” to “Direct3D11”
- Restart Unity Editor
- Select “Assets/NewComputeShader“
- In the Inspector Window check the “CSMain” property
Expected result: “CSMain” property is updated accordingly to the selected API
Actual result: “Compute Shader” asset is not reimported, “CSMain” property is not changed
Reproducible with: 2020.3.41f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b15, 2023.1.0a18
Reproducible on: Windows 11
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2020.3.46f1):
Fixed the editor compute shaders to work correctly independent from the re-imports.