Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.27f1
2021.2.9f1
2022.2.0a2
Issue ID
UUM-5746
Regression
No
Planar Reflection Probe always forces objects to be rendered when occlusion culling is baked
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/Bugs
3. Go to the Game view and enable the Stats overlay
4. Press the Play button and observe the number of Tris drawn
5. Press the Play button again to exit Play mode
6. In the Hierarchy window, select the GameObject "Planar Reflection"
7. Disable the GameObject by disabling the checkbox next to its name in the Inspector view
8. Press the Play button and observe the number of Tris drawn
Expected result: the number of triangles drawn is around 1.4M before and after disabling Planar Reflection
Actual result: the number of triangles drawn is around 3.6M before disabling Planar Reflection
Reproducible with: 10.8.1 (2020.3.27f1), 12.1.4 (2021.2.9f1), 13.1.5 (2022.1.0b5, 2022.2.0a2)
Could not test with: 7.7.1 (2019.4.35f1) (HDRenderPipelineAsset.CreatePipeline errors)
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
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
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.