Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0f2
Issue ID
1047096
Regression
No
HideFlags does not work on instantiated prefabs when using a custom class
To reproduce:
1. Open the QA's attached project
2. Open the scene "SampleScene" and play it
3. Go over all selections in the custom "Tools" menu
4. Notice that the 2nd selection "CustomClassNotWorking" does not hide the prefab in the Hierarchy
Expected result: The instantiated prefab is hidden when using the custom class
Actual result: The instantiated prefab is visible in the hierarchy
Reproduced with: 2017.2.3f1, 2017.4.5f1, 2018.1.5f1, 2018.2.0b9, 2018.3.0a1
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 warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (2018.3.X):
Setting hideflags on a component does not propagate to the GameObject and other components, this give you fine grained control over the hideflags on each component. The exception is the Transform component which will recursive through the children.