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
Comments (1)
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
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
- [Android] [iOS] Application silently crashes when creating and setting up Textures2D in large amounts
- Some VFX Window Panels close on entering Play mode
- VFX Graph using Redo action for Move and Connect node results in an unknown input value
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?