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
5.0.0b17
Issue ID
658853
Regression
No
[deferred] Decals done via cmdbuffers don't get lighting/probes/lightmaps
Since ambient + reflection probes + lightmaps are done as part of g-buffer rendering, then any further modification of g-buffer (e.g. by decals via rendering command buffers) is not affected by ambient/probes properly.
There are no good solutions for this, it seems.
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
- 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
Font8
Jul 01, 2015 02:02
Same. I was looking use this implementation, but ambient light just doesn't pull from the modified g-buffers. Must be rendering ambient light early before I can get to modify them.