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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Compute shader toggle is independent from the graphics shader toggle. Both save the state.