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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
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