Search Issue Tracker
Fixed in 2019.3
Fixed in 2018.3, 2019.1, 2019.2
Votes
0
Found in
2018.3.0a6
2018.3.0f1
Issue ID
1107231
Regression
Yes
MonoBehaviour cannot be added to prefab instance or prefab asset if it contains Particle System component
Steps:
1. Create a new project
2. Add any script to Assets (default "New MonoBehaviour" is enough)
3. Add "GameObject -> Effects -> Particle System" GameObject to Hierarchy
4. Drag it to Project browser to make a prefab asset
5. Select Particle System instance
6. Drag and drop script to Inspector
==>
Restructure prefab instance dialog appears (expected: script is added as override)
7. Open prefab and drag script to inspector
Restructure prefab instance dialog appears (expected: script is added to asset and merged to instance)
Workarounds:
1. Drag script on top of prefab instance
2. Add script through "Add Component" button
3. Add other component and then add a script though Inspector
Take a look into attache movie for details
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
- Crash in StackAllocator::TryDeallocate when calling ParticleSystemRenderer.BakeMesh
- Modifying scoped registries in project manifest does not update Package Manager UI window
- Models change their position in scene when reimporting them in 2019.4
- Texture 'Read/Write' option does not double the memory in Profiler
- [Particle System] Ribbon trails are connected in the wrong order when moving the Particle System with faster movements
vorefaka
Feb 15, 2020 08:02
Different systems have different components than other as some are external components and some are internal. As soon as possible https://best-essay-writing.services/essaypro-com-review/ only works with the internal components because it cannot handle the external ones.