Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.2p1
Issue ID
958320
Regression
No
[Emission] Adding a burst while multi-selecting particles with non-matching bursts produces undesirable results
Repro steps:
1. Open Scene1 from the attached project.
2. Observe the two particle systems in the scene; one has no bursts, the other has 1 burst.
3. Select both systems and observe how in the inspector it appears that none of them have any bursts
4. Add a new bursts
5. Observe how both systems have the same bursts (i.e. even though only 1 burst was added, the first system inherited the pre-existing burst).
Expected outcome: only the new burst to be added.
Notes:
- seems a bit far-fetched to want to multi-add a burst on systems with different pre-existing bursts. Maybe just disable the functionality if the selected systems have different bursts?
- not a regression, reproes in 2017.1 up to 2018.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 3D Sample Scene (HDRP) template tutorial Welcome Dialog pop-up doesn't appear on project creation
- [Profiler] The Addressable Asset Module module outputs an ArgumentException when asset GUIDs produce a hash collision with Addressables
- Huge amounts of tests have a start delay when pressing "Run All" in the Test Runner
- Blackboard: Double borders around the tooltip
- [WebGL]VideoPlayer Rendering stops when setting FilterMode of a texture downloaded with UnityWebRequestTexture.GetTexture()
Add comment