Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2021.2.15f1
2021.3
2022.1
2022.2
Issue ID
1416421
Regression
No
HideFlags is not working when compilation is finished
How to reproduce:
1. Open the attached "1416421.zip" project
2. Open the SampleScene Scene found in the "Assets/Scenes" folder
3. Expand the Parent GameObjects
4. Open the "MakeNotEditable.cs" Script
5. Uncomment the code with "HideFlags.HideInHierarchy" (Line: 10)
6. Return to the Editor
Expected Result: The HideFlags start working after recompilation
Actual Result: The HideFlags work only after restarting the Editor
Reproducible with: 2019.4.38f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Resolution Note (fix version 2022.2):
Fix for this issue will be available on Unity 2022.2.0a16 and above