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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment