Search Issue Tracker
By Design
Votes
0
Found in
2019.2.0a10
Issue ID
1144394
Regression
No
Editor shaders not recompiling when changing target graphics API in the player settings
Changing Graphics APIs between DX11/DX12 doesn't result in shaders being recompiled in-Editor.
Reproduction Steps:
1. Open the new attached project (case_1142554-DX12_RenderTexture_bug.zip)
2. Switch the Editor to DX11 (Player Settings, PC/Mac/Linux, ensure D3D11 is top of the list)
3. Select the file "Scenes/ComputeStencilTest.compute", observe "Direct3D11 Direct3D12" (correct)
4. Switch the Editor to DX12 (requires an Editor restart)
5. Select ComputeStencilTest.compute
Expected Result:
The Kernels for the shader should list "Direct3D12 Direct3D11"
Actual Result:
The Kernels for the shader list "Direct3D11 Direct3D12"
Workaround:
Right click and Reimport the shader, observe the update to "Direct3D12 Direct3D11"
Reproducible in versions 2019.2.0a11, 2019.1.0f1, 2018.3.13f1.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2019.3.X):
It is expected that no reimport happens as no APIs were added or removed.