I noticed this problem starting in 4.16, but it seems like it’s still an issue in 4.17.
When you’re importing a lot of fbx meshes and set the “import uniform scale” to anything other than 1.0, some of the geometry gets imported at the new scale, while others remain at 1.0. Which results in something like this:
I have taken a look and gone through some repro steps provided, and I believe the results are similar to what you are seeing. I would like to make sure that these are the same issues though. If you could provide some more screenshots/information I can be sure of this. The steps that I took are as follows: Created 3 different meshes in Maya. The sizes were set to centimeters in Maya which is what UE4 uses (64cm, 24cm, and 4cm). I then exported them all out of Maya at a scale of 1.0 as FBX files. Then imported them into 4.17 at the same time. I did this a few times, each time changing the Import Uniform Scale number. The result each time was 3 different meshes on top of each other that were each a different size.
Does this sound like the result that you are getting?
I drag all of these meshes into the content browser to import. I choose an “Import Uniform Scale” setting of 30.48 to convert the scale to cm (having exported it in feet). I hit import all.
Some of the meshes get imported at the new appropriate scale of 30.48. While others stay at a scale of 1 despite saying that they are 30.48 in the static mesh window.
So the bug is basically that after a certain number of meshes get imported, it stops imported at the “import uniform scale” that you set in the import settings and defaults back to 1.0.
I was able to recreate this issue and have logged it as a bug. If you would like to keep an eye on the bug you can track it using this link. If you have anymore questions regarding this thread let me know.
The problem is worst than what is in bugtracker description: Once imported, you can set differents values in “import scale uniform” of those imported mesh assets, hit save then clic on reimport and this value will be ignored.
The import scale issue is happening in 4.20.3 with MegaScans assets (though it doesn’t seem to happen with meshes we’ve created). The “Convert Scene Unit” suggestion below doesn’t make any difference either. The only way to affect the static mesh scale post import is to generate blueprints and nest them. This problem doesn’t happen in 4.22p2.