Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in [Package]
10.2.0
Issue ID
1294584
Regression
No
[SRP] GameObject from incorrect Layer is getting rendered with Occlusion culling when stacking Cameras
How to reproduce:
1. Open the attached "1294584_repro.zip" project
2. Open the "SampleScene" Scene
3. Go to Window -> Rendering -> Occlusion Culling
4. Press "Bake" in the Inspector
5. Select the "Main Camera" GameObject in the Hierarchy window
6. Observe the Game view
Expected result: Image from UI Layer is getting rendered with the UI Camera
Actual result: GameObject from the Default Layer is getting rendered with the UI Camera
Reproducible with: 7.5.1 (2019.4.15f1), 8.2.0 (2020.1.15f1), 10.2.0 (2020.2.0b13, 2021.1.0a7)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment