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.
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
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.