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
0
Found in
2019.4
Issue ID
1312443
Regression
No
[Enlighten] Systems, Clustering, Lit Clustering, and UV Charts scene debug views are broken
Steps to reproduce:
1. Download and open ArchVizPRO Vol.2 project (link in the comments)
2. Open scene AVP_Interior_Vol.2
3. Generate realtime GI using settings provided in the scene
4. Once precompute is complete, switch to any of the Global Illumination scene debug views (Systems, Clustering, Lit Clustering, UV Charts)
5. Notice how the viewport is either completely blank, or filled with rendering artifacts
Notes:
- Affects both Enlighten Realtime GI and Baked GI
- Only the aforementioned debug views are affected; others are not
- More likely to reproduce with high Indirect Resolution values, and High Resolution lightmap parameters asset
- When using low Indirect Resolution values, and Low Resolution lightmap parameters, affected debug views are more likely to work and/or rendering with artifacts
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
- 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
Resolution Note (2021.2.X):
This will be solved as part of a larger area refactor.