Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a6
2018.3.0f2
2019.1.0a1
Issue ID
1114369
Regression
No
Dragging a component from Prefab Mode into an Inspector field of a Scene object does not set the component in the field
How to reproduce:
1. Open the "New Unity Project.zip" project and open the scene "SampleScene"
2. Select "GameObject" in the Hierarchy and lock it in the Inspector
3. From the Project window, open the prefab "Camera Prefab" in a different Inspector window
4. Drag the Camera component from the prefab into the "Anything" field on the "GameObject"
Expected result: The "Anything" field now shows a reference of the Camera component
Actual result: Assigning the Camera component to the field does not work
Reproduced with: 2018.3.2f1, 2019.1.0a13
Notes:1. By editing the Scene file through a text editor you can still set the Anything field to reference the Camera component from the prefab (this is shown in the provided video)
2. Not tested in 2017.4 because the bug is related to Improved Prefabs which were only introduced in 2018.3.0a6
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 Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note (2019.2.X):
If you select a Prefab in the Project Browser and drag one of its components to the object field of a object in the Scene this works fine since you are dragging the imported Prefab Asset component. But when you open a Prefab Mode the objects opened are part of a sandbox scene where you edit the Prefab contents. These objects cannot be dragged to the scene since they are temporary objects that are destroyed when Prefab Mode is exited.