Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2
2018.3
2018.3.9f1
2019.1
2019.2
Issue ID
1141584
Regression
No
IPreprocessShaders passes zero length data list when lighting data is baked
Steps to reproduce:
1. Load the attached project
2. Open the test scene
3. Make sure the lighting data is cleared using "Clear Baked Data" on the Lighting window
4. Build the project and see the following output from the shader preprocessor:
Strip: 1 / Unlit/Unlit
Strip: 12 / Custom/ShaderVariantsStripping
(See that the number printed is correctly showing the number of variants for that shader)
5. Under the shader window press the "Generate Lighting" button
6. Wait for it to complete
7. Clear the console window, save the scene
8. Build the project again and see the following output:
Strip: 0 / Unlit/Unlit
Strip: 0 / Custom/ShaderVariantsStripping
(See that the number printed is 0 incorrectly reporting the number of variants for that shader)
Actual result: with a baked scene the shader preprocessor gets passed a zero length data list.
Expected result: with a baked scene the shader preprocessor should get a non zero length data list.
Reproducible: 2018.3.11f1, 2019.1.0b9, 2019.2.0a10
IPreprocessShaders was added in 2018.2
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Every few months we look at bugs which we have not had the opportunity to fix yet. We try to be as diligent as we can and want to prioritize bugs that are causing issues with shipping and frequent pain points in day to day works. To ensure we are targeting the most important bugs we regularly close out older bugs that have not reached this threshold over the past months. The bug you have currently raised has not met this threshold for fixing over the last few months.