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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment