Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.8f1
2022.1.13f1
2022.2.0b4
2023.1.0a5
Issue ID
UUM-11528
Regression
No
Particle System Trails are connected to the wrong particle after removing a particle that was created with “emit()”
How to reproduce:
1. Open project “PrototypeProjectileSystem.zip”
2. Enter Play Mode
3. Wait 20 seconds and observe the Game view
Expected result There are no straight Trails created
Actual result: There are straight Trails created
Reproducible with: 2021.2.0b6, 2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a5
Could not test with: 2020.3.37f1, 2021.2.0b5 (Errors after project downgrade)
Reproduced on: macOS 12.4 (Intel)
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
- Shader Keywords are not detected when defined in include files
- Right-clicking on Blackboard and Graph Inspector calls the contextual menu of the workspace
- [Android][Vulkan]Shader casting issue occurs when using Snapdragon devices with the Vulkan Graphics API
- "Paste" option is available in Shader Graph contextual menu even when the clipboard has unrelated item
- Editor crashes when debugging a for loop
Resolution Note:
We can't easily support using SetParticles with trails, other than to modify existing particles.
Any use of SetParticles that sets more or less particles back to the system than it previously had, will cause problems with the trails data, because it is stored separately from the ParticleSystem.Particle data.
Instead, it should be possible to set the same particles back, but with remainingLifetime set to -1 for any particles you wish to remove.