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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment