Similar issues occur with Revit as Revit System Units are Feet/Meters and 3ds Max System Units are inches by default. If you import an FBX file from Revit that uses “Imperial: Feet” as system units into 3ds Max while the 3ds Max default units are inches, the FBX conversion scales all objects in the scene during the import process.
The Revit scale is 12.0 (or 12 inches per foot). This is because, if the scaling did not occur, your units would become one foot = one inch which would then create distortion in any bitmap used in the scene.
For example, if you do not scale objects upon import, a Revit imported house ends up with walls that are 12 inches long, instead of 12 feet long. The FBX conversion scaling is also done to ensure that bitmaps are mapped properly in size in relation to the objects in the scene. If your wall is 12 feet long, it has to be converted to 144 inches long for the bitmap used to display in an appropriate real-world scale.
If you want to exchange FBX files between 3ds Max and Revit, change your System unit settings to feet to match Revit.
We do not recommend that you change the FBX Revit Import preset Units setting in the so that the scale units are feet instead of inches. It is true that if you do this, you create a 1:1 match for objects and avoid any scaling conversion. However, if you change the Revit Preset units setting so that no conversion is performed, all units become non-real-world and then materials do not render at the right scale.
If you do not want to change the 3ds Max default System Units, there is another work-around for this scaling problem; manually convert every object to real world scale after you import the file into 3ds Max. If you do this, you must have Inches set as system units, which is the 3ds Max default.