Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.40f1
2021.3.11f1
2022.1.17f1
2022.2.0b8
2023.1.0a12
2023.2.0a1
Issue ID
UUM-17800
Regression
No
Child Prefabs disappear from Prefab hierarchy when applying the "Optimize Game Objects" option
How to reproduce:
1. Open the attached project “FBXPrefab.zip“
2. Open the Prefab “MyPrefabVariant“ Hierarchy (Assets)
3. Attach the “TestPrefab01“ Prefab (Assets/Prefabs) to the “arms_AuxSHJoint” child GameObject
4. Exit the “MyPrefabVariant“ Prefab Hierarchy
5. Select the “mdl_runaway“ FBX file (Assets/runOp)
6. Enable “OptimizeGameObjects“ and hit “Apply“
Expected result: The attached child Prefab “TestPrefab01“ exists in the “MyPrefabVariant“ Prefab Hierarchy
Actual result: The attached child Prefab “TestPrefab01“ doesn’t exist in the “MyPrefabVariant“ Prefab Hierarchy
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a12
Reproduced on: macOS (12.5), Windows 10
Note: When trying to reproduce the issue, if the 4th step is skipped, the “TestPrefab01“ Prefab doesn’t disappear, but detaches from the parent GameObject
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.