Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.6.0f3
Issue ID
899256
Regression
No
Setting hideFlags to HideFlags.None on a component breaks the prefab
To reproduce:
1. Open attached project
2. Select Cube prefab in Project view
3. Right click on Hideflagstest script component on the prefab and select Do Not Push Me (it sets HideFlags to None)
4. Reimport Cube prefab by right click -> Reimport
5. Observe prefab
Expected: setting HideFlags to None does not break the prefab
Actual: settign HideFlags to None breaks the prefab
Reproduced in 5.5.2p4, 5.5.3f1, 5.6.0f3, 2017.1.0b1
Postponed: Will be fixed as part of the new prefab workflow
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment