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
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Resolution Note (fix version 2019.3):
Distance bands should be fixed in 2019.3.