Search Issue Tracker
Fixed in 10.2.0
Votes
0
Found in [Package]
9.0.0-preview.35
Issue ID
1241626
Regression
No
Soft Particles do not fade out near the opaque surfaces when Post Processing is enabled on a Stacked Camera
How to reproduce:
1. Open the attached project "1241626.zip"
2. Open the "Test" Scene
3. Enter the Play Mode
4. Select the "FX Camera" GameObject in the Inspector window and uncheck the "Post-processing" checkbox under the "Rendering" settings of the Camera component
Expected result: no hard edges appear where soft particles intersect with an opaque surface
Actual result: hard edges appear where soft particles intersect with an opaque surface
Reproducible with: 2019.4.2f1 (URP version: 7.3.1, 7.4.1) , 2020.1.0b13 (URP version: 8.1.0), 2020.2.0a15 (URP version: 9.0.0-preview.35)
Could not test with: 2018.4.24f1 (URP version: 4.10.0) and earlier as Camera Stacking is not introduced in these versions
Workarounds:
- Enabling "Clear Depth" option under "Rendering" settings of the Camera component fixes the issue
- Switching Main Camera's Anti-aliasing to None or FXAA - fixes the issue
- Switching Anti Aliasing (MSAA) to "Disabled" under URP Asset Quality settings fixes the issue
Note: tested and reproduced with Direct3D11, Vulkan and OpenGL Core APIs
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 (fix version 10.2.0):
The issue has been fixed in Universal Render Pipeline 10.2.0 and above.