Short technical notes on moving a model between Autodesk Revit and Autodesk 3ds Max. Each one answers a single question in its first sentence, and shows the evidence underneath.
They exist because the published answers to these questions are often wrong, out of date, or accurate about the problem while stopping short of what to do about it.
All notes
| Revit File Link or FBX for 3ds Max? The usual advice recommends each one for the phase where its weakness costs the most. |
| Do Revit and 3ds Max versions have to match? Not exactly. There is backward tolerance of three releases and no forward tolerance at all. |
| What happens to deleted Revit elements in 3ds Max? They are removed on the next reload, with the materials and modifiers on them, and there is no undo. |
| Why modifiers and UVW break when a Revit link reloads Modifiers store index numbers, not geometry. A reload reassigns those numbers. |
| What Combine By Revit Material actually does to your model It fuses every element sharing a material into one object, and takes element identity with it. |
| Why “Keep material parameters on reload” doesn’t save your 3ds Max materials The option protects material parameters. It does not protect material assignments. |
| Does Datasmith move a Revit model into 3ds Max? No. Both of its exporters write for Unreal Engine. |
| Can Speckle sync Revit and 3ds Max? No. Speckle has no 3ds Max connector. |
| Is NVIDIA Omniverse still a Revit to 3ds Max route in 2026? Not on current releases. The connectors stop at the 2024 versions of both applications. |
What these are not
They are not product tutorials. Levlin Bridge appears in most of them because it is the reason we know these details, and it is named where it is relevant and nowhere else. Where another tool is the right answer — Datasmith for Unreal Engine, Speckle for Rhino and Blender, FBX for a frozen model — the notes say so.
Reference documentation lives separately, on GitHub: the version matrix, the layer map and the Safeguard behaviour.