Search Issue Tracker
By Design
Votes
0
Found in
2020.1.0a18
2020.2.0b8
Issue ID
1285353
Regression
No
[Caching Shader PP] Compute shader does not save its "Preprocess only" state
Compute shader does not save its "Preprocess only" state.
Steps to repro:
1. Create a new project.
2. Edit > Project Settings > Editor > Shader Compilation.
3. Enable Caching Preprocessor.
4. Project Settings > Click on "+" > Shader > Unlit Shader.
5. Select Unlit Shader > Inspector > Enable Preprocess only.
6. Create "Compute Shader" > Select > Inspector.
Actual Result:
Compute shader does not save its "Preprocessor only" state.
Expected Result:
Compute shader saves its "Preprocessor only" state.
Reproducible in:
2020.2.0b8, 2020.1.10f1, 2020.1.0a18.
Note: Cache Preprocessor introduced in 2020.1.0a18
Environment:
Occurring on Windows 10 & Mac 10.15.
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
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
- 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
Resolution Note:
Compute shader toggle is independent from the graphics shader toggle. Both save the state.