Because modifiers do not remember your geometry — they remember index numbers. An Unwrap UVW, an Edit Poly, a UVW Map applied to a face selection: each one stores which vertices and which faces it acts on, by number. Reload a Revit link and those numbers are reassigned. The modifier is still there, still pointing at index 4,182, and index 4,182 is now a different piece of the building.
This is why the failure looks so strange. The modifier has not been deleted. It is doing exactly what it was told, to the wrong geometry.
The mechanism, step by step
| Step | What happens |
|---|---|
| 1 | You apply a modifier. It records a sub-object selection as a set of vertex and face indices. |
| 2 | The Revit model changes. Not necessarily the element you worked on — anything that alters how the file is tessellated will do. |
| 3 | The link reloads. The incoming geometry is rebuilt, and vertex and face numbering is assigned afresh. |
| 4 | Your modifier evaluates against the new numbering. The selection now covers different faces, or faces that no longer exist. |
The result ranges from mapping that has slid across a surface to a modifier that throws away its selection entirely.
Why it happens to elements you did not touch
This is the part that makes it feel random. Adding detail somewhere else in the model can change face counts on import, and once counts change, numbering changes with them. An element nobody edited can come back renumbered because of a decision taken in another part of the building.
Why the material options do not help
The two material options in the File Link reload settings are the first thing everyone reaches for, and they address a different layer of the problem. They can carry material parameters across a reload. They do nothing about vertex and face numbering, because that is not what they are for.
A separate field note covers what those options actually protect and what they leave exposed: Why “Keep material parameters on reload” doesn’t save your 3ds Max materials.
What reduces the damage today
| Measure | Where it helps | Where it stops |
|---|---|---|
| Never use Combine By Revit Material | Keeps elements as separate objects, so renumbering is contained to the element that changed. | Does not make numbering stable within an element. |
| Prefer real-world mapping over face-selection mapping | Mapping that does not depend on a stored sub-object selection survives renumbering. | Not an option for anything that genuinely needs a manual unwrap. |
| Keep the link intact — never collapse to Editable Poly | Collapsing ends updates entirely, which trades one problem for a worse one. | The link keeps renumbering. |
| Do the modifier work last | Less exposure, because there are fewer reloads left to survive. | Only works if the design is actually finished. |
Each of these avoids the problem rather than solving it. It is solved only where object identity is stable across revisions.
What stability would mean
If an element that did not change in Revit is not rebuilt on the receiving side, its numbering is never reassigned, and a modifier that referenced index 4,182 still means the same thing after the update as before it.
That is the property Levlin Bridge is built around. Only the elements whose source geometry actually changed are rebuilt. Everything else is left alone, so materials, modifiers and UVW stay where you put them — not because they are copied back, but because nothing disturbed them.
Frequently asked
Why do my UVW modifiers break when I reload a Revit link?
Modifiers store sub-object selections as vertex and face index numbers. Reloading rebuilds the incoming geometry and reassigns those numbers, so the modifier evaluates against different faces than the ones you selected.
Why does it affect objects I did not edit in Revit?
Changes elsewhere in the model can alter how geometry is tessellated on import. Once face counts change, numbering changes with them, and an untouched element can come back renumbered.
Do the Keep material options in the reload settings protect modifiers?
No. They act on material parameters. Vertex and face numbering is a different layer of the problem and those options do not address it.
Does collapsing to Editable Poly fix it?
It stops the renumbering by ending the link, which also ends updates from Revit. That is trading the problem for a bigger one.
Is there a way to keep modifiers across updates?
Only where object identity is stable. If an element that did not change is never rebuilt, its numbering is never reassigned and the modifier keeps meaning what it meant.
Related field notes
- Why “Keep material parameters on reload” doesn’t save your 3ds Max materials
- Do Revit and 3ds Max versions have to match?
- What happens to deleted Revit elements in 3ds Max?
- What Combine By Revit Material actually does to your model
- Does Datasmith move a Revit model into 3ds Max?
- Can Speckle sync Revit and 3ds Max?
- Is NVIDIA Omniverse still a Revit to 3ds Max route in 2026?
- Revit File Link or FBX for 3ds Max?
Levlin Bridge
Levlin Bridge is a Windows plug-in that moves geometry between Autodesk Revit and Autodesk 3ds Max in both directions. Push the model from Revit, pull it into 3ds Max, and push the geometry you changed back into Revit as real elements. Only the difference ever moves, so materials, modifiers and UVW stay exactly where you left them. Any Revit 2022–2027 works with any 3ds Max 2024–2027.
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.