Search Issue Tracker
By Design
Votes
0
Found in
2018.1.5f1
Issue ID
1054212
Regression
No
Shader settings are not being enabled/disabled by the Script when the Game is Built
Reproduction steps:
1. Open user's attached project ("TestEmissionBug")
2. Enter the playmode and click on the cube
3. Inspect change of cube's shader
4. Build and run the game
5. Click on the cube, inspect that shader did not change
Expected: Shader settings change both in Editor and in the Built Game
Actual: Shader settings do change in Editor, but do not change in the Built Game
Reproduced in: 2017.2.3p2, 2017.4.7f1, 2018.1.9f1, 2018.2.1f1, 2018.3.0a6
Update:
Unused shader settings are excluded from the build and can not be modified in the Built Game.
Workaround: Creating second material with enabled settings and switching to it in Built Game.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment