Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f3
Issue ID
822767
Regression
No
Changing the standard shader render mode via script doesn't work in build
Steps to reproduce:
1. Create a new Unity 3D project
2. Import attached Unitypackage
3. Open "Demo" scene
4. Press play
5. Try to move the ball behind red obstacles using WASD keys
6. Notice how red obstacles become transparent ("editor.gif" attached)
7. Exit play mode
8. Build and Run on Windows
9. Repeat step no. 5
10. Notice how red obstacles don't become transparent ("player.gif" attached)
Expected behavior: red obstacles get transparent like in Editor
Reproduced with: 5.3.6p2, 5.4.0f3, 5.5.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Add comment