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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (2019.3.X):
It is expected that no reimport happens as no APIs were added or removed.