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
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- Error "InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings." is present when using UI Toolkit and New Input System
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
- [Linux] The mouse wheel input is inverted when scrolling in the Build
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