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
- Project Auditor's "Install Rules" button has to be pressed twice to proceed when any compilation error in the Editor is present
- Crash on Scripting::UnityEngine::SubsystemManagerProxy::ClearSubsystems when adding a Mesh Collider Component to a GameObject
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
Add comment