Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.3.X, 2019.1.X, 2019.2.X
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
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.