Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a9
Issue ID
UUM-53182
Regression
No
Mesh Renderer is frozen when there are duplicate Static GameObjects
How to reproduce:
1. Open the attached project "Essentials.zip"
2. Enter Play Mode
Expected results: "FallingSphere" and "FallingSphere (1)" are falling in the Game view
Actual results: "FallingSphere" and "FallingSphere (1)" are not falling in the Game view
Reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a9
Reproducible on: Windows 11 22H2
Not reproducible on: No other environment tested
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
This issue is happening because the two spheres are marked Static, and therefore they are combined to a single, static world-space mesh by the Static Batching which is enabled in Player Settings. Objects that are marked Static are not expected to be moved at runtime, which is the case here.
The reason why it behaves differently with a single sphere is that with a single static object, there is nothing to combine and therefore static batching is effectively disabled in this case. However, this is incidental behavior/optimization that shouldn't be relied upon. The root issue here is that static objects are being moved at runtime.
Resolution Note (2023.3.X):
This issue is happening because the two spheres are marked Static, and therefore they are combined to a single, static world-space mesh by the Static Batching which is enabled in Player Settings. Objects that are marked Static are not expected to be moved at runtime, which is the case here.
The reason why it behaves differently with a single sphere is that with a single static object, there is nothing to combine and therefore static batching is effectively disabled in this case. However, this is incidental behavior/optimization that shouldn't be relied upon. The root issue here is that static objects are being moved at runtime.