Search Issue Tracker
Won't Fix
Won't Fix in 2021.2.X
Votes
1
Found in
2020.3.5f1
2021.2.0a14
Issue ID
UUM-5742
Regression
No
[Culling API] Multiple Assertion failed errors get thrown when ScriptableRenderContext.Cull is called with more than 6 culling planes
How to reproduce:
1. Open the user's attached project
2. Open Assets > ProjectorForLWRP > Test > CullingTest Scene
3. In the Hierarchy select the Main Camera
4. Observe the Console
Expected result: There are no visible errors present
Actual result: Multiple 'Assertion failed on expression' errors appear in the Console
Reproducible with: Universal RP 7.6.0 (2019.4.24f1), 10.3.2 (2020.2.7f1), 10.4.0 (2020.3.5f1), 12.0.0 (2021.2.0a14)
Cannot test with: 2018.4.34f1 (the package is not supported), 2021.1.3f1 (Internal build system error. Backend exited with code -1073741819.)
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
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- SetComponentEnabled uses class instead of struct when constraining Enableable Component type
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
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.
Resolution Note (2021.2.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.