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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2020.3.46f1):
Fixed the editor compute shaders to work correctly independent from the re-imports.