Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0f1
Issue ID
1036508
Regression
No
GeometryUtility.CalculateFrustumPlanes() and GeometryUtility.TestPlanesAABB() are not returning the right values
It seems that GeometryUtility.CalculateFrustumPlanes() and GeometryUtility.TestPlanesAABB() are not returning the right values, and this can be seen more easily when the geometry is big. For small geometry there is still a problem but since the distances are smaller it is not aas visible.
To reproduce:
- Open scene LightUtilsWindow_Bug
- Open menuitem TechArt > Light Utils window.
- Select the Spot Light in Hierarchy
- Put Sceneview in Orthographic Topdown view
- Notice the Cube is Red, which means it's in frustum of the blue spotlight - this is the problem: you can see that the spotlight (and temporary camera) are not touching the cube, yet it identifies as it is (attached screenshot f1)
- Move the cube around and notice that other cases are fine (attached screenshot f2)
Reproducible: 2018.3.0a1, 2018.2.0b13, 2018.1.0f2, 2017.1.1p3
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
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
- Graph and Camera options for Render Graph Viewer disappear after maximising the window
Xarbrough
May 28, 2019 14:30
What is the reasoning behind this design? Performance? And what is the recommended way of working around this limitation? I've added a rough bounds or sphere intersection check to my code before using TestPlanesAABB, but I use it everywhere, so I wonder in which cases I wouldn't want this to be part of the function itself?