Search Issue Tracker
Won't Fix
Votes
8
Found in
2017.3.0b9
Issue ID
969240
Regression
No
Setting the cameras culling matrix breaks culling for oblique matrices
Steps to reproduce:
1. Open the attached project
2. Open "TestScene"
3. Select Main Camera
4. Select "Use Projection Matrix"
5. Visualize Occlusion Culling
6. After moving around the main camera notice that occlusion culling is properly working
7. Untick "Use Projection Matrix" from the Main Camera
8. Visualize Occlusion Culling and after moving the camera notice the broken Occlusion Culling
Expected result: setting an oblique Camera.cullingMatrix should not break culling
Reproduced in: 2018.1.0a4, 2017.3.0b9, 2017.2.0p2, 2017.1.2p3, 5.6.4p
Comments (1)
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
MCudlitz
Nov 30, 2017 01:56
Currently suffering from this, which is crippling the overall performance of my VR application. Currently, adding any kind of effect camera for water, reflection of any kind, portals, or any other special image effect incur the additional cost of rendering the entire scene regardless of what is occluded, turning something that should at worst halve performance into something that can slash it to 10% of what it should be.