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
- [MotionVectors][RenderingDebugger][MSAA] Render Graph Execution error and black Game View when enabling MotionVectors overlay in the Rendering Debugger with MSAA
- "[Project Auditor] Could not find any registered modules." warning is thrown when clicking "Start Analysis" and the rules were installed while there are compilation errors in the Editor
- “ArgumentException: Object that does not belong to a persisted asset cannot be set as the target of a LazyLoadReference" is thrown when changing Unsupported Selector Action and saving in UI Builder
- Cursor image flickers in Viewport preview when unsupported Texture 2D is assigned to element
- [HDRP] Game view is rendered black when using Pathtracing on a HDR display
Add comment