Search Issue Tracker
Duplicate
Votes
0
Found in
4.3.0b5
Issue ID
569433
Regression
No
Adding component that requeres own base class adds extra component to the object
If you add to object component like this:
[RequireComponent(typeof(B))]
public class A : B {}
Component B will be added to the object.
Object should have only A.
It is not consistant with behavior in similar situations:
a) when A requeres A (then there will be only one A component)
b) when A requeres some other component B1, but object already has component A1 (where A1 inherits B1), B1 will not be added.
After you add A to an empty object, B will be added.
If you try to delete B you'll get an error "A depends on B". So you should delete A first and then B.
But if you add another A, you'll get one component B and two A. Then you can delete B. And after that you can delete one A. Last A cannot be deleted because of the bug 568895
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
This is a duplicate of issue #568895