Search Issue Tracker
Fixed in 2021.3.15f1
Fixed in 2021.3.X, 2022.2.X, 2022.2.0f1, 2023.1.X
Votes
0
Found in
2021.3.4f1
2022.2.0a16
Issue ID
UUM-7797
Regression
No
Incorrect near planeSize.y calculation at CameraEditorUtils.cs
In the 'TryGetSensorGateFrustum' method in the CameraEditorUtils.cs (https://github.com/Unity-Technologies/UnityCsReference/blob/master/Editor/Mono/Inspector/CameraEditorUtils.cs) the near plane size calculation is different form far plane size and includes a typo.
Far: planeSize.y = camera.farClipPlane * Mathf.Tan(Mathf.Deg2Rad * camera.fieldOfView * 0.5f);
Near: planeSize.y = 2.0f * camera.nearClipPlane * Mathf.Tan(Mathf.Deg2Rad * camera.fieldOfView * 0.5f);
The near planeSize.y multiplication by 2 seems incorrect as it is not required and has not been spotted before as the near plane calculation is never called in any editor code and the near vector array is always passed in as null so the conditional check always skips that part of the code.
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a16
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment