Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.7f1
2019.3
2020.1.0a9
Issue ID
1190085
Regression
No
PostProcessEvent.BeforeTransparent does not work on LWRP for custom postprocessing effect
Steps to reproduce:
1. Open User-supplied project
2. Open and run Scene "SampleScene"
3. Open and Enable the Frame Debugger.
Expected: to see post-processing effects on their cube when their post-processing effect is tagged with PostProcessEvent.BeforeTransparent
Actual: no post-processing shows unless tagged with PostProcessEvent.AfterStack or PostProcessEvent.BeforeStack
Reproduced in: 2017.4.33f1, 2018.4.11f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a9
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
The Lightweight render pipeline isn't supported anymore and we encourage people to move over to the Universal render pipeline (which will be part of the 2019 LTS version).