Search Issue Tracker
Won't Fix
Votes
7
Found in
2018.4.26f1
2019.4.8f1
2020.1.2f1
2020.2.0a20
2023.2.0a1
Issue ID
UUM-5819
Regression
No
Representation of LOD Group bounds are displayed not fully containing shapes when camera is rotated
How to reproduce:
1. Open attached project "LODGroupBounds.zip"
2. Open "WrongLODGroupBounds" scene
3. Open Scene Window
4. Select "WrongLODGroupBounds" GameObject
5. Rotate Scene View camera around and observe LOD Group bounds around the model
Expected result: LOD Group bounds fully contain the shape
Actual result: LOD Group bounds do not fully contain the shape
Reproducible with - 2018.4.26f1, 2019.4.8f1, 2020.1.2f1, 2020.2.0a20
-
Aeime
Nov 19, 2021 02:27
I have also seen this issue.
-
iendsl
Nov 19, 2021 01:29
My friend is also having this issue
-
tcjkant
Nov 19, 2021 01:23
The issue is related to camera FOV. If the camera is orthographic, the bounds are correct. The wider the FOV, the more mismatched the bounds become.
If your application requires a high FOV (ex. a VR project), it is possible for the mismatch to be so extreme that the LODGroup component will start LODing the model down even if you are standing on top of part of it (so the view percentage should clearly be 100%).
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.