Search Issue Tracker
Fixed in 2022.1.X
Votes
1
Found in
2018.4
2019.4
2020.3
2021.1
2021.2
2021.2.0a8
Issue ID
1320649
Regression
No
Model file to Unity scaling is defined as "1m (File) to 100m (Unity)" when importing Blend file
Reproduction steps:
1. Open the user's attached project
2. In the Project window, select Test.blend asset
3. In the Inspector window, select Model and observe the scaling values
Expected result: 1m (File) to 1m (Unity)
Actual result: 1m (File) to 100m (Unity)
Reproducible with: 2018.4.32f1, 2019.4.22f1, 2020.3.0f1, 2021.1.0b11, 2021.2.0a8
Comments (1)
-
sameng
Oct 28, 2021 00:31
Looks like this change may be causing a big incompatibility with previous versions of Unity.
In all previous versions, blend files were imported at the same scale definition.
This change breaks that. All previous projects with blend files will be broken in 2022 due to this change.
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a6