Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.43f1
2021.3.16f1
2022.2.2f1
2023.1.0a24
Issue ID
UUM-27533
Regression
No
Prefab's Transform Rotation is altered when imported from Blender
Reproduction steps:
1. Open the attached project “BlenderImportBug“
2. Open “Assets/Scenes/SampleScene.unity“ Scene
3. Open “Assets/BlenderFile.blend“ in Blender
4. Drag “Assets/BlenderFile.blend“ into the Scene
5. Select “BlenderFile“ GameObject in the Hierarchy window
6. Observe the “Rotation“ of the Transform Component in the Inspector window and in Blender
Expected result: The “BlenderFile“ GameObject has the same “Rotation“ Transform in Unity and Blender
Actual result: The “BlenderFile“ GameObject Transform “Rotation“ property “X“ is “-89.98”
Reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a24
Reproducible on: Windows 10
Note: Changing Transform Rotations in Blender and saving causes all rotations to change in Unity, but they do not match. If the Blender Prefab has a camera after deleting it in Blender and saving rotations of the GameObject in Unity are reset.
*{*}About the -89.98x rotation{*}*
This can be avoided by exporting the model as an .fbx and using the 'Apply Transform' option in Blender's FBX exporter.
Know that It does come with a warning about possibly affecting animations and armatures and is tagged experimental.
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 Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
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.