Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.1.0a6
2022.1.0a12
Issue ID
1376387
Regression
Yes
GameObject scale is too small when importing .blend Models
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Observe the GameObjects in the Scene view
Expected result: the GameObjects "polyman", "cube (1)", and "cube (2)" are similar in size to "cube"
Actual result: the GameObjects "polyman", "cube (1)", and "cube (2)" are too small to be visible in comparison to "cube"
Reproducible with: 2022.1.0a6, 2022.1.0a13
Not reproducible with: 2019.4.32f1, 2020.3.21f1, 2021.1.27f1, 2021.2.1f1, 2022.1.0a5
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2022.1.X):
In 2022.1 we updated our code to better respect the scale which is passed to us via DCCs (including Blender).
However, from some debugging we can see that Blender changed their file scale between 2.79 & 2.8 - & right now we're not factoring in older versions (pre-2.79) in our code path.
We'll look at doing just that. In the meanwhile, we would suggest either using Blender 2.8+, or changing the scale factor on imported models.