Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.3.0b6
Issue ID
962226
Regression
No
CullingGroup's distance bands are inaccurate
To reproduce:
1) Open attached project and scene
2) Make sure you have both Scene and Game views visible and separated (i.e. they are not using the same window tabbed).
3) Select Cube in hierarchy
4) Lock the inspector (so you could follow the values in "Test" component)
5) Play the scene
6) Drag the camera towards and outwards the cube
Expected: The Distance Band changes at 10 distance from both ends. (nearestDistanceFromSphere is 10)
Actual: It roughly takes about 11.2 for the Distance Band to change
Reproduced in 2017.1.0f3, 2017.3.0b6, 2018.1.0a3
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 warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (fix version 2019.3):
Distance bands should be fixed in 2019.3.