Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0b5
Issue ID
910051
Regression
No
Particle Trails 'Color over Lifetime/Trail' use a single colour by default
How to reproduce:
1. Open any (new) project
2. Create a Particle System
3. Enable the 'Trails' option
4. Try to set the Color over Lifetime
- Note that a color picker pops up, rather than a gradient editor window
- This is confusing as everywhere else in the Particle Editor, where "Colour over X" is defined, it uses a Gradient editor by default
- Single colour should be removed, or set to not be default in this situation
- By Design until more complaints are received.
- Reproduced with 2017.1.0b5 (e2f219641e2c), 5.5.3p2 (f15b2772e4d0)
Comments (1)
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
aaforcebox
Jun 14, 2017 16:47
I can't use this property as well. I needed to change at runtime, either setting a gradient or single color, and nothing works. I can choose a color on Inspector, though (not a gradient, just a single color).