The FBX import/link or 3ds Max does not create layers based on the file content.

Run this script on freshly imported Revit models via FBX.  It will move all objects on a Layer that corresponds to the Category and Family as illustrated:

It will also restore original Meta data into Parts which are imported without Categories Names, Family Names and Family Types Names.

This script is not a plugin and does not save data in the scene.  You only need to run it on demand.  Note that some entities imported via FBX do not contain meta data from Revit (this is a bug on the Revit side).  Those entities, typically railing posts, lights and parts will remain untouched and left on their original layer.

Note: this assumes that the meta data is available after the FBX import or link. In other words, using Combine by Material will get rid of the Meta information about families (because objects get combined togheter).

Click here to download the script

Or what about listing the type of object as well as its material name and type?

This can be done with a relatively simple MAXScript that you must install  under the \Scripts\Startup directory of your 3ds Max installation.

By doing so, the script will execute each time 3ds Max is launched and will  instruct the Scene Explorer to fetch data about your objects and create new columns that you can drag and drop in place:

• Material Name
• Material Type
• Object Plugin Type
• Layer Name

Save Target as… to download the MAXScript

Save Target as… to download the SceneExplorer.ini file that you can load from the Tools > Manage Scene Explorers dialog.

1. In Revit, go in the 3D view you will export to FBX
2. Edit the Graphic Display Options
3. Specify a Location and Time that matches your project settings, for a single day:

   

4. Export to FBX
5. Import in 3ds Max

Your Daylight System should now match the Revit model in Location and Time.

To get rid of those edges, you can hide them from the editable mesh panel:

Or better, use a Maxscript tool that will let you hide them all at once.

Click here to download the MaxScript

Usage: Select all your EditableMesh objects and execute the script. The script will only affect selected EditableMesh objects so the selection can contain lights, lines, cameras: they won’t be affected by the script.

The result:

Special Thanks to Chris P. Johnson who helped improving the speed and stability of the script on large models containing several instances.

The size of the FBX files exported by Revit is influenced by the following aspects:

Model size:

Obviously, the more details in your 3D view, the larger it will be.  There is not much you can do about it besides controlling the way your families are drawn (fine, medium, coarse display settings).

Texture Maps used by the Render Appearances:

All textures used by the Revit materials are embedded in the exported FBX for portability reasons. On one hand, this is useful because you don’t have to bother about file paths issues (“texture not found” errors) but it has a cost in terms of file size. If you don’t render in Revit, you might want to think about editing your materials in a way that textures are not used at all.  This way, the exported FBX file will not contain additionnal image files.

Environment Maps:

Revit defaults to a rendering setting that uses a texture map for clouds.  This texture map on itself weights about 20Mb and cannot be compressed more. Since it is also zipped up with the exported FBX models, you take a 20Mb hit right away. To resolve this issue, switch the render settings of Revit to use a clear sky (no clouds). Doing so will remove the large clouds image file and reduce the size of the exported FBX file.