The checkbox protects material parameters. It does not protect material assignments. When a Revit File Link reload changes the identity of an object in 3ds Max, the incoming object is a new object — and a new object takes its material from the Revit source, not from the work you did in Max. That is why artists report losing V-Ray and Corona setups with the option switched on.
The two things the option does not do
File Link exposes material protection as separate switches, reading roughly as Keep 3ds Max material parameters on reload and Keep 3ds Max material assignments on reload. They are not the same thing, and neither covers modifiers or UVW mapping.
| What you did in Max | Survives a reload? |
|---|---|
| Material settings — colour, reflection, maps, IOR | Usually, if the material still exists in the scene |
| Which material is applied to which object | Only if object identity is preserved |
| Modifiers on the object — Edit Poly, Shell, Bend | No guarantee — lost when the object is rebuilt |
| UVW Map / Unwrap UVW | No guarantee — lost when the object is rebuilt |
| Layer membership and object names | Frequently change |
The pattern behind every row is the same: everything you built in Max is attached to an object. If the reload replaces that object, everything attached to it goes with it.
Combine By Revit Material is the one to avoid
Of the grouping options, Combine By Revit Material does the most damage, and it does two kinds of damage at once.
It destroys element identity
Autodesk documents the behaviour plainly: with By Revit Material, all Revit entities assigned the same material become a single 3ds Max object, named after the material and placed on a layer named after the material.
Autodesk — File Link Settings: Revit and FBX Files Dialog
Read what that means on a real project. Two hundred walls sharing one Concrete material do not arrive as two hundred walls. They arrive as one mesh called Concrete. The element boundaries are gone; what is left is a single object made of loose faces. You cannot select one wall, you cannot isolate one surface, and you cannot give one element its own treatment.
Displacement is where this becomes unworkable. A displacement is applied per object. On a merged mesh it applies to every element fused into it at once — the wall you wanted and the two hundred you did not. Getting displacement onto a single surface means detaching faces by hand, and detaching breaks the link that was the whole reason for using File Link. The workaround costs more than the feature saves.
Autodesk’s own note adds that Multi/Sub-Object material information is lost under this option — so the merged object also loses the structure that would have let you address its parts separately.
It makes the grouping key a material name
Whether an existing Max object is updated or replaced on reload depends on how incoming entities are grouped. With material as the key, renaming a material in Revit, splitting one, or merging two changes the grouping — so the objects on the Max side are no longer the same objects. They are rebuilt, and once rebuilt they carry the Revit material, not yours.
There is a further documented failure: combining on link is associated with geometry arriving offset from its correct position, and Autodesk’s published workaround is to choose Do Not Combine Entities — which is to say, to switch the feature off.
Autodesk Support — Objects are offset or moved from original position when using Link FBX in 3ds Max
Why object identity breaks
Beyond grouping, the reload can write incoming geometry as new objects on the current layer while leaving the original objects behind as empty placeholders. The scene then holds both, and none of your Max-side work is on the geometry you can actually see.
Documented cases
The option was checked, and the materials still reset
“The correct geometry is loaded, but is now on the current layer rather than the previous layer named for the Revit model. It is also an Editable Mesh, not linked. Strangely, the ‘old’ objects in the Revit named layer are still there as empty objects called ‘default’ in the Modify tab. Materials on the new objects are set back to the original state and don’t reflect changes that had been made to them in Max, even though ‘Keep material parameters on reload’ is checked.”
Two details matter. The model was linked with Combine by Material. And the thread has one reply — this is not a settings mistake with a known answer.
The same complaint, ten years earlier
“When it reloads the materials get all messed up. If I uncheck those boxes and reload, it comes in clean, but then it erases all of the material changes I’ve made to my scene. I can’t keep redoing the same changes every time I need to reload.”
Autodesk has acknowledged the class of problem
“This happens on pretty much every job and we have to manually correct the model. A complete waste of time and energy. […] I spoke to Autodesk last week and these are known issues.”
Chaos Forum — “Revit FBX → Link FBX 3ds max. Shifting geometry.”, June 2021
And it is still open in 2026
“Support has informed me that I should remove the current Revit interop and install version 25.4.41.14. Support says they are unable to recreate the issue with 25.4.41.14, which is another way of saying that the latest updates are indeed broken on their side and reverting to an older version is the current solution.”
What actually helps — and where each measure stops
These are the free measures worth taking. None solves the underlying problem, and it is worth being clear about where each one ends.
1. Never use Combine By Revit Material
Use By Revit Category, or do not combine at all. This is the single highest-value change you can make: it keeps element boundaries and removes material names from the grouping key. Where it stops: category grouping is still rebuilt when the category contents change.
2. Give every Revit material a unique, specific name
Glass_Curtainwall, Glass_Railing, Glass_Door — not one Glass for the whole project. Where it stops: it reduces accidental merging; it does not preserve anything you did in Max.
3. Check both material options, not one
Parameters and assignments are separate switches. Where it stops: as the 2025 case shows, checking them is not sufficient when object identity changes.
4. Keep the link intact — never collapse to Editable Poly
Collapsing breaks the link permanently. Where it stops: this is not a solution, it is a constraint. It means “do not modify the geometry you were hired to make look good.”
5. Detach a workshared model before linking
Link a detached copy rather than the central model, so Max does not hold the central file open. Where it stops: it is a workaround for file locking, not for material loss.
6. Rebuild manually
The honest fallback, and the one most studios actually use: reapply materials, re-add modifiers, remap UVWs. Where it stops: it costs hours per revision, every revision.
The structural point. Every measure above is about avoiding the reload, working around it, or absorbing its cost. None makes a reload safe, because File Link has no persistent identity for a Revit element across reloads. Without stable identity there is nothing to attach your work to.
What a fix would have to do
Any tool that genuinely solves this has to do three things File Link does not:
- Persistent element ID mapping — a stable identity for each Revit element that survives across updates, independent of material name, category or file version.
- Differential update — update only elements that actually changed; never touch objects whose source did not change.
- Material identity decoupled from geometry update — the material assignment lives on the Max side and is never rebuilt from the Revit source.
The sequence has to be: Revit changes → resolve element ID → update geometry only → leave material, modifiers and UVW untouched. Not: delete objects → create new objects → reassign materials from source.
Levlin Bridge
Levlin Bridge is built on exactly that: ID-mapped differential transfer between Revit and 3ds Max, elements arriving whole and separately selectable rather than merged by material, and materials, modifiers and UVW preserved on every element whose source geometry did not change. Any Revit 2022–2027 works with any 3ds Max 2024–2027, so no version matching is required.
Levlin Bridge is in final testing and is not released. There is nothing to download yet. Leave your email and you get the 30-day trial the day it ships.
Frequently asked
Does “Keep 3ds Max material parameters on reload” preserve my V-Ray or Corona materials?
It preserves the parameters of materials that still exist in the scene. It does not guarantee that those materials stay assigned to the right objects. When a reload changes object identity, the assignment is rebuilt from the Revit source and your Max-side assignments are lost.
What is the difference between material parameters and material assignments?
Parameters are the settings inside a material: colour, reflection, maps, IOR. Assignment is the link between a material and a specific object. File Link exposes two separate options for these, and checking only the parameters option leaves assignments unprotected.
Why is Combine By Revit Material the worst option?
Because every Revit element carrying the same material becomes one single 3ds Max object. Two hundred walls become one mesh named after the material. You can no longer select an individual wall, and any modifier you apply, a displacement above all, applies to every element merged into that object at once.
Why do reloaded Revit objects come in as Editable Mesh instead of linked geometry?
In some reload scenarios the incoming geometry is written as new objects on the current layer rather than replacing the existing linked objects. The old objects can remain in the scene as empty placeholders. Because the new objects are new, they carry no Max-side material or modifier history.
Is there a setting that fully protects modifiers and UVW maps on reload?
No. File Link has no option that guarantees modifiers and UVW mapping survive a reload when the source geometry changes. Modifier and UVW work survives only as long as the underlying object is unchanged.
Do Revit and 3ds Max versions have to match to use File Link?
File Link depends on the Autodesk Revit Interoperability component, which is version specific. Mismatched or partially mismatched releases are a recurring cause of link failures, including a June 2026 case where Autodesk support recommended reverting to an older interoperability build.
All quotations are verbatim from public forum threads, with dates as shown on the original posts. Every source is linked inline.