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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Add comment