Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3
2021.2
2022.1
Issue ID
1342106
Regression
No
Player and Editor don't behave the same when creating GameObjects at runtime and setting colors
Reproduction steps:
1. Open the attached "MakeARedCube.zip" project
2. Open and play the Scene "scene" -> note that the cubes are respectively white and red
3. Build And Run -> note that both cubes are pink.
Actual result: Different behavior between Editor and Build
Expected result: Similar behavior between Editor and Build
Reproducible in: 2020.3.13f1, 2021.2.0b2, 2022.1.0a1
Could not test in: 2019.4.28f1 and 2018.4.36f1 (because of serialization errors)
Add comment
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
Resolution Note:
The Standard shader is being culled from the build output as nothing in the build is referencing it. By adding a reference to the Standard shader in the Always Included Shaders list, or by a material used in a Scene or Resources folder will resolve the issue.