Search Issue Tracker
Fixed in 5.3.7
Votes
0
Found in
5.4.0b15
Issue ID
813671
Regression
No
LOD Group incorrect extents after mesh is combined and bounds are recalculated
Steps to reproduce:
1. Open the attached project (lodetest.zip)
2. Open 'lodtest' scene
3. Select game object 'lodroot' (notice the Extents are 2.67m)
4. Click 'batch them' button in Test component
5. Press Recalculate: Bounds button in LOD Group component
Expected result: mesh group extents should cover the combined mesh
Actual result: extents turn to 1.00m (bounds don't cover combined meshes)
Reproduced with 5.4.0b24, 5.3.5p8, 5.2.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment