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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2019.3):
Distance bands should be fixed in 2019.3.