Search Issue Tracker
Fixed in 2019.3.X
Votes
2
Found in
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1171312
Regression
Yes
Warning says instancing will be disabled when used with static batching but it is still working and breaking result object color
To reproduce
Just open the attached project and scene inside
Expected: The cube is green
Actual: The cube is red
Reproduced in 2018.3.0a1, 2018.4.0f1, 2019.1.0a1, 2019.3.0a11
Not reproduced in 2017.4.29f1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.3):
This issue is actually by design. What you see is that the Editor and Player mode don't necessarily render in exactly the same way. Particularly in this case, static mesh batching doesn't happen until the Player launches and the scene is built. Hence, while in Editor, instancing can still be done, which is exactly what is seen. The warning message itself has been updated to clearly indicate that instancing will be disabled *when the Player is active*.