Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.8f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1175460
Regression
No
Asset Importers for models default the Scale Factor value to 1 regardless of the model extension
How to reproduce:
1. Download the user-submitted model(1x1x1cube.jas)
2. Create a new Unity project
3. Import the downloaded model
4. Select it in the Project View and see the import settings
Expected result: Scale Factor is defaulted to a value, appropriate for the asset extension(in this case - 0.01 for .jas)
Actual result: Scale Factor always defaults to 1
Reproducible with: 2017.4.31f1, 2018.4.6f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a12
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
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
- Game View Tab Scale changes erratically when a Unity Tab is on a different screen with a differing Display Scale
- Six way lighting receiving wrong lighting from APV when set to World Space
- Crash on SortByExecutionOrder when interrupting the .androidpack import process
Resolution Note (2020.1.X):
Cheetah3D does not have a precise definition of its unit. In Unity, when the fbx conversion is done to import the asset, the fbx sdk reports it as a meter unit. In 2017 we fixed our scripts to use what is being declared in the fbx sdk value instead of a fixed custom value, hence the size change in newly imported Cheetah files.
We do not want to introduce any new custom values in this conversion process and it will stay with the current scale factor.
The documentation and manual does not mention the custom scale values since the 2017 version of Unity, which matches the current behavior.
However, it is possible to create a default partial Preset applied to all .jas files that would set the global scale factor to 0.01 and get the older behavior back in your project.