Search Issue Tracker
Fixed
Fixed in 2020.2.7f1
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-1936
Regression
Yes
[Backport] [XR SDK] [URP] Occlusion culling is inoperative
Reproduction steps:
1. Open the attached project ("1304299Repro.zip")
2. Make sure MockHMD is enabled (Project Settings->XR Plug-in Management)
3. Open "BugScene" scene
4. Open Occlusion window (Window->Rendering->Occlusion Culling)
5. Open Scene window, set Occlusion Culling to Visualise and Enable Visibility lines
6. Observe the objects that shouldn't be rendered
7. Enter Play mode
Expected result: Only objects that are in the range of Visibility Lines are rendered
Actual result: Occlusion culling is not working, all scene is rendered (see "jtB9tsCiPw.mp4" video)
Reproducible with: URP 10.2.2 (2020.2.2f1, 2021.1.0b2)
Not reproducible with: URP 7.5.2, 8.3.1. 9.0.0-preview.72 (2019.4.17f1, 2020.2.2f1)
Could not test with: 2018.4.30f1 (XR SDK not available)
Tested:
- MockHMD
- Oculus Rift S
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