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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
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.