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
- [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
Add comment