Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4
2019.4
2019.4.19f1
2020.3
2021.1
2021.2
Issue ID
1332277
Regression
No
"This Renderer uses static batching and instanced Shaders" warning is thrown even when Static Batching is disabled
How to reproduce:
1. Open the user's attached "MisleadingWarningInstancedMeshes.zip" project
2. Open the "SampleScene" Scene
3. Select the "Cube" GameObject in the Hierarchy window
4. Observe the Mesh Renderer Component Inspector window
Expected result: No warnings in the Mesh Renderer Component
Actual result: "This Renderer uses static batching and instanced Shaders." warning in the Mesh Renderer Component
Reproducible with: 2018.4.34f1, 2019.4.24f1, 2020.3.5f1, 2021.1.5f1, 2021.2.0a15
Note:
- Full warning message: This Renderer uses static batching and instanced Shaders. When the Player is active, instancing is disabled. If you want instanced Shaders at run time, disable static batching
Comments (2)
-
charcreon
Jun 23, 2023 08:04
I migrated a project from 2021.3.5 to 2022.3.2 and now it happens...maybe not in a clean environment...
-
kingkrayz
Dec 14, 2021 17:57
This issue is reproducible in version 2021.2.6f1
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
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
- "Multiplayer Center" window does not reflect changes made in "Other Packages" section
- Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
- Editing and saving Curve changes in UI Builder window throws multiple errors in the Console
- [UI Builder] Value is not selected when left clicking on Spacing/Border Widget values
Resolution Note (fix version 2022.1):
Fixed in: 2021.2.0a20
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.13f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.14f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.29f1