Search Issue Tracker
By Design
Votes
0
Found in
2018.2.14f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1123744
Regression
No
Shader with cleared ShaderCompilerData is still present in the build files
Steps to reproduce:
1. Open original project "ShaderStripping.zip"
2. Build it on Windows platform
3. Open Build\ShaderStripping_Data\globalgamemanagers with Unity Asset Bundle Extractor (https://github.com/DerPopo/UABE/releases)
Expected result: There shouldn't be cleared shader in the build file
Actual result: There are remains of the cleared shader in the build file
Reproduced in: 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Note:
1. Could not test in 2017.4 because Shader striping script has missing references.
2. Editor strips the PostProcessing/SSR shader.
3. If there are errors with Post Processing Stack, just delete it and re-download Post Processing Stack from Asset Store.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] 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
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
The callback was only designed to add / remove variants of a shader from a build, not remove a shader all together. To do the later, remove the shader from the "Assets\PostProcessing\Resources\Shaders" folder so it is not included by the Resources system when it builds.