Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.0f3
Issue ID
874706
Regression
No
An instance of a prefab does not update the text in Edit mode while dragging the new material on it in the Scene window
Reproduction steps:
1. Open the attached project;
2. Open the scene "Scene";
3. Disable an object "Not A Prefab" and clear Console window;
4. Click on "SomeMaterial" in Assets folder and drag it on the object "Prefab With Native Script" in the Scene window (do not drop the material, just keep it on the object);
5. Observe Console window output;
6. Enable an object "Not A Prefab" and disable "Prefab With Native Script", clear Console window;
7. Click on "SomeMaterial" in Assets folder and drag it on the object "Not A Prefab" in the Scene window (do not drop the material, just keep it on the object);
8. Observe Console window output;
Actual result: when the process is done with an object "Not A Prefab", in the Console window you can see that the text becomes longer with letter "a" per frame (NotAPrefab.gif). When the process is done with an object "Prefab With Native Script", in the Console window you can see the same text which is in the Inspector window (PrefabWithNativeScript.gif).
Expected result: the process with "Prefab With Native Script" should act like with "Not A Prefab".
Note: In Edit Mode, an object which is a prefab and has the script "SomeScript" does not update the text when you are dragging the material over it. If you are moving the object, than the text is updated. This is happening just with an instance of a prefab that includes the script. Also, if you drop the material on the object and try drag the same one on the object, everything works correctly. The bug appears just in Edit Mode, if you try to comment it and enter Play mode, everything will be correctly.
Reproduced with: 5.3.6p4, 5.4.4f1, 5.5.0f3, 5.6.0b6, 2018.3.0a7
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
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- 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
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.