Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.4.X
Votes
0
Found in
2017.4
2018.4
2018.4.11f1
2019.2
2019.3
2020.1
Issue ID
1193339
Regression
No
Standard Surface Particle shader reveals objects behind the GameObject with the shader when using certain Rendering Modes
How to reproduce:
1. Open the attached "UnityDeferredParticles.zip" project
2. Load "SampleScene" scene (found in "Scenes" folder)
3. Enter the Play mode
Expected result: quad with "Particles/Standard Surface" shader does not reveal GameObjects behind it
Actual result: quad with "Particles/Standard Surface" shader reveals GameObjects behind it
Reproduced with: 2017.4.33f1, 2018.4.12f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a9
Notes:
- reproduced with "Cutout", "Additive" and "Modulate" Rendering Modes for "IssueParticleShader" ("Particles/Standard Surface" shader)
- "Standard" shader with "Cutout" Rendering Mode does not have this issue ("Additive" and "Modulate" Rendering Modes not available)
- the issue is not visible in Isometric mode
- one workaround would be to set Rendering Mode to either "Opaque" or "Fade" or "Transparent" for "IssueParticleShader"
- another workaround would be to set Rendering Mode to any other than "Cutout" for "BG", that is used for the GameObjects that are behind the quad with "IssueParticleShader"
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
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.1f1