Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.7f1
2023.2.0b2
Issue ID
UUM-45655
Regression
No
Child GameObject position is different in the DAE file from the FBX file when using "Bake Axis Conversion" in Import Settings
Reproduction steps:
1. Open the attached project “FBX_DAE”
2. In the Project window select the “Assets/dae_u_avoid01.DAE” file
3. In the Inspector window make sure that the “Bake Axis Conversion” checkbox is enabled
4. Repeat steps 2 and 3 for the “Assets/fbx_u_avoid01.FBX” file
5. Open the “Assets/Scenes/SampleScene” Scene
6. In the Hierarchy window select dae_u_avoid01 → top_null → all_move → cam_001 → attach_002 child GameObject and look at its position in the Scene view
7. In the Hierarchy window select fbx_u_avoid01 → top_null → all_move → cam_001 → attach_002 child GameObject and compare its position to the position of dae_u_avoid01 child GameObject position
Expected result: Both child GameObjects appear in the same position
Actual result: The GameObjects appear in different positions
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b2
Reproducible on: macOS 13.4.1 (c)
Note: The child GameObjects appears in the same position if “Bake Axis Conversion” is disabled for both GameObjects in the Import Settings
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.