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
- “[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