Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.1
2020.2
2020.2.0a20
Issue ID
1267266
Regression
No
[shuriken] multiple instances of sub emitter are created with the same name for Particle system
while creating and assigning Particle system as Sub Emitter, When multiple times same Particle system is created and assigned as Sub Emitter, then multiple instances of sub emitter are created with the same name for a Particle system. refer attached video
Steps to repro:
1. Create a new project
2. Hierarchy > right-click > Effects > Particle System
3. Inspector > Particle System > Enable Sub Emitters
4. Sub Emitters > Select Particle System > Particle System
5. Create and assign Particle system as Sub Emitter >(+)
6. Repeat steps (4-5)
7. Observe Hierarchy >Particle System > SubEmitter0
Actual Result:
multiple instances of sub emitter are created with the same name for Particle system
Expected Result:
multiple instances of sub emitter should be created with the differentiable unique name for Particle system (ex.SubEmitter0, SubEmitter0_1, SubEmitter0_2)
Reproducible in:
2020.2.0a20, 2020.1.1f1, 2019.4.6f1, 2018.4.26f1, 2017.4.38f1
Environment:
Windows 10 and macOS 10.15
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This is so minor, but a fix is non-trivial, so it will never be prioritised.
Finding a unique game object name would require searching the current GameObjects. This could become very bad for performance on large scenes. It just doesn't seem worth spending time on this.