Search Issue Tracker
Fixed in 5.13.0
Votes
0
Found in [Package]
2.0.1
Issue ID
1112983
Regression
Yes
[LWRP] Shaders are not included in the build when their name contains 'Debug' string
How to reproduce:
1. Open tester-submitted project (ShadersDebug)
2. Open the 'SampleScene' scene
3. Build and Run the project
Expected result: both cubes are rendered in the built player
Actual result: the cube that uses the 'Test-Debug' shader is not rendered in the built player
Reproducible with: 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Could not test with: 2017.4.23f1(LWRP unavailable)
Reproducible with LWRP Package versions: 2.0.1, 5.7.2
Not reproducible with LWRP Package versions: 1.1.11
Regressed LWRP Package version: 2.0.1
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (fix version 5.13.0):
Fixed in LWRP 5.13.0 and 6.7.0. Removed the debug string check in the shader stripper