Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
2019.4.20f1
2020.1.0a24
2020.3
2021.1
2021.2
2021.2.0b9
2022.1
Issue ID
1363211
Regression
Yes
Material isn't assigned back on Particle Trails when disabling and enabling Trails
Reproduction steps:
1. Open the attached project "trail_sample.zip"
2. Open the "SampleScene" Scene
3. Select "Particle" GameObject from "Object" > "Particle" in the Hierarchy
4. In the Inspector window disable Trails
5. Enable the Trails
6. Observe the Scene View
Expected result: The Trails material is assigned automatically
Actual result: The Trails material isn't assigned and stays pink
Reproducible with: 2019.4.20f1, 2019.4.30f1, 2020.1.0a24, 2020.3.19f1, 2021.1.22f1, 2021.2.0b12, 2022.1.0a10
Not reproducible with: 2019.4.19f1, 2020.1.0a23
Note:
- To skip 3-5 steps enter the Play mode, Trails will be disabled and enabled automatically
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
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
- Lighting data is carried over from one Scene to another when changing Scenes in the Play Mode
- The <sprite> tag inserted image from a Sprite Asset into the UI Builder Button disappears when the Inlined Style Text Shadow Horizontal or Vertical Offset is set to be more than 0 px
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a16
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.9f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.31f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.38f1