Search Issue Tracker

Won't Fix

Won't Fix in 2021.3.X

Votes

0

Found in

2021.3.19f1

Issue ID

UUM-30680

Regression

No

Orthographic Projection affects CameraCullPlanes when using custom Projection

Culling

-

Steps to reproduce:
1. Open the attached project “IssueProject“
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. In the Hierarchy window expand the “CameraRig“ GameObject and select the “Main Camera“ GameObject
4. In the Inspector window set the Projection to Orthographic
5. Change the Size value while looking at the “Camera Cull Planes” list values
6. “Camera Cull Planes” list values are synced
7. Enable the “Use custom Proj“ option
8. Change the Size value while looking at the “Camera Cull Planes” list values
9. “Camera Cull Planes” list values are still affected

Expected result: CameraCullPlanes are not affected by Orthographic Projection when using a custom Projection
Actual result: Orthographic Projection affects CameraCullPlanes when using custom Projection

Reproducible with: 2021.3.19f1
Couldn’t test with: 2020.3.46f1, 2022.2.9f1, 2023.1.0b7, 2023.2.0a4 (couldn’t upgrade/downgrade the URP package because it’s custom)

Reproducible on: Windows 10

Notes:
1. Only reproducible with the custom URP 12.1.8 package
2. Issue does not occur when using Perspective Projection

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (2021.3.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.