Quiet Tools Studio
FBX imports at the wrong size
The error factor is the number the file declares divided by the number the program assumed. Nearly every "my model is 100× too big" is one of three cases, and they have three different fixes.
The arithmetic, once
Let d be what the file declares (centimetres per unit) and a what the
program assumes. Everything you see is out by d ÷ a. A file declaring
1 (centimetres) opened by something that assumes metres: 100× too big. A
file declaring 100 (metres) opened by something that assumes centimetres:
100× too small. Same file, opposite symptoms — which is why "it's too big" and "it's
too small" are not two problems but one, seen from two sides.
The three cases
| What the file says | What you see | What it usually means |
|---|---|---|
a very small factor — 0.01, 0.1 |
the model is a speck, or huge when someone "corrects" it by 100 | the scene was built at the wrong scale and exported anyway. The declaration is the bug, not the geometry. |
1 or 100, and it disagrees with the pipeline |
exactly 100× out, in one direction | centimetres and metres: the file declares one and the consumer assumes the other. The fix is either the file or the import setting — and only one of those travels with the asset. |
a factor that differs from OriginalUnitScaleFactor |
the model is the size it should be in one program and wrong in another | something converted this file after export. Consumers that honour the declaration get it right; anything that assumes its own units gets it wrong by the ratio. |
Why the import setting is a workaround, not a fix
A Scale Factor or a Convert Units checkbox lives in a project, attached to an asset — not inside the file. It is not delivered with the model, it does not survive being re-imported elsewhere, it is not what a client or a marketplace reviewer receives, and the next person to open the asset has to know it was set. A correct declaration is part of the file and needs no explanation.
What a small factor is not
It is not automatically an error. Millimetre CAD workflows legitimately declare
0.1, and a pipeline that agreed on it end to end is fine. The question is
never "is this number unusual" but "does the rest of the pipeline agree with
it" — which is what a platform profile answers, and why the report says what a
factor means in metres rather than only printing it.
Check a folder instead of guessing
FBX Scale Report reads a folder of FBX files and prints what each one declares — the factor, what it means in metres, whether the file contradicts itself — and measures the rig the way an engine will read it. It reads the files rather than importing them, so nothing enters your scene, and it names the files it could not read instead of staying quiet about them. Free, read-only, no account.
Changing the declaration rather than reading it is what the paid edition does, with a preview of every change and a record of what it wrote: FBX Scale Report Pro.