Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.1.1f1
2020.2.0a18
2020.2.0b4
Issue ID
1282252
Regression
Yes
When editing multiple Particle Systems at the same time, the properties don't get set for all of them
Reproduction steps:
1. Open user's attached project "ImportBug.zip"
2. Open the "SampleScene"
3. In the Hierarchy window select multiple GameObjects "Particle System", "Particle System(1)" and "Particle System(2)"
4. In the Inspector window change the values of " Start speed ", "Start Size", "Simulation speed" and "Start Color"
Expected result: All values of selected properties change on selected Particle Systems
Actual result: Not all values of selected properties change on selected Particle Systems
Reproducible with: 2020.1.1f1, 2020.1.7f1, 2020.2.0a18, 2020.2.0b5
Not reproducible with: 2018.4.27f1, 2019.4.11f1,2020.1.0f1, 2020.2.0a17
Note:
- When changing the values again with multiple selected Particle Systems, every value will be changed and the issue will disappear
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a8
Resolution Note (fix version 2020.2):
Fixed in 2020.2.1f1