Search Issue Tracker
By Design
Votes
0
Found in
2018.2.10f1
Issue ID
1086746
Regression
No
Using "Dynamic Batching" causes visual differences between Scene and Game view Game Objects
Reproduction steps:
1. Open "New Unity Project (1).zip" project
2. Look at the Scene view and notice two cubes with one side painted blue
3. Look at the Game view and notice one cube with one side painted blue and the other cube with one side painted yellow and the opposite side painted blue
Expected Result: Scene and Game view Game Objects are displayed the same
Actual Result: Using "Dynamic Batching" causes the Game Objects to be displayed differently between the Scene and Game view
Reproduced with: 2019.1.0a7, 2018.3.0b8, 2018.2.14f1, 2018.1.9f2, 2017.4.14f1
Note:
After just starting the project, in the Scene view both cubes are blue and in the Game view both are yellow. After doing anything in the Editor, one of the Game view cubes turns blue.
In 2018.1 the "yellow" cube is multicolored
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:
Realtime GI will also has a realtime lightmap baked for the objects (no matter they are lightmap static or not), and when directional lightmaps are used, the object tangents will be modified.