Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X
Votes
0
Found in
2020.2.4f1
2020.3.12f1
2021.1
2021.2
2022.1
Issue ID
1346626
Regression
Yes
Material appearance changes when Shader is using #pragma multi_compile_particles
Reproduction steps:
1. Extract and open the attached project (MCPIssue)
2. Open scene Scenes/SampleScene
3. Observe the two spheres in the Scene view
Expected result: Both spheres look the same
Actual result: The spheres look different
Reproducible with: 2020.2.4f1, 2020.3.13f1, 2021.1.15f1, 2021.2.0b3, 2022.1.0a2
Not reproducible with: 2018.4.33f1, 2019.4.28f1, 2020.2.3f1
Note:
- The only difference between the shaders is that one uses '#pragma multi_compile _ SOFTPARTICLES_ON' whereas the other one uses '#pragma multi_compile_particles'
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
- “Handles.Repaint called outside an editor OnGUI" error is thrown in the Console when creating a new Tile Palette from the Tile Palette Overlay in Scene view
- UI Shader Graph’s Main Preview has a right-click context menu with different preview options which do not work for a UI Shader Graph and does nothing when clicked
- Shader Graph window icon is blurry and low quality when the Shader Graph is created using the Universal 2D template
- “Export HDRP Sky to Image” command error message does not indicate that Game view must be visible
- Adaptive Performance Settings Framerate field doesn't display the "supported without VSync" warning, when the field is collapsed in Build Profiles
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a14
multi_compile_particles was mutually exclusive with other built-in variant creating pragmas. In this particular case the surface shader was trying to use multi_compile_fwdbase but then the multi_compile_particles came after that and its keywords were added instead of the built-in lighting keywords. This is now fixed so that the particles keywords will be added on top of other potential built-in keywords, similar to how multi_compile_fog works for example.