Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.2
2019.3
2019.3.0b10
2020.1
Issue ID
1198492
Regression
No
3D object loses its Shader in the build when there is a Local keyword in Nested Shader
Steps to reproduce:
1. Open User's attached project "ShaderFeatureLocalStrippingIssue-2019.3.zip"
2. Open SampleScene
3. Enter Play mode
4. Notice the Cube is blue
5. Build and Run the project
6. Notice the Cube is white
Expected results: The 3D object is Blue
Actual results: The 3D object loses its Shader in the build when there is a Local keyword in Nested Shader
Reproducible with: 2019.2.13f1, 2019.3.0b11, 2020.1.0a13
Note: Shaders in the project do not work with Unity 2018.4.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment