Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
1
Found in
2018.4.0f1
2019.2
2019.2.10f1
2019.3
2020.1
Issue ID
1199466
Regression
Yes
Reference to component in prefab sometimes references component in prefab asset instead of instantiated object
To reproduce:
1. Open attached project ("PrefabComponentReferencing.zip")
2. Open Sample Scene
3. Look at ReferenceTestOK under ComponentReferenceTest prefab in the scene
4. click on the referenced light field and note how it highlights the referenced light object under the prefab in the scene (OK)
5. look at ReferenceTestNG under ComponentReferenceTest prefab in the scene
6. click on the referenced light field and note how it highlights a folder in the project window (NG)
7. look at ReferenceTestNGbutOK under ComponentReferenceTest prefab in the scene
8. click on the referenced light field and note how it highlights the referenced light correctly. presumably since the array is empty it doesn't trigger any of the mistaken serialization
Expected result: "ReferenceTestNG" light field should highlighted referenced Game Object in the Scene
Actual result: Assets folder is highlighted
Reproducible in: 2018.4.0f1, 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a15
Not reproducible in: 2017.4.35f1
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
- Pausing a Visual Effect doesn't pause the “Multiply size over life” effect in the Update Block
- Wheel Colliders aren't detecting collision
- [VFX Graph] VFX graph is still dark when using Light Mode
- The Rotation of Child GameObject with the Interpolating RigidBody is set to a random number when changing the Rotation of Parent GameObject
- [Shader Graph] Shader graph is still dark when using Light Mode
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a11
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b10
Resolution Note (fix version 2019.3):
Fixed in 2019.3.15f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.24f1