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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment