They are removed from your scene, silently, on the next reload. That is not a bug and it is not a setting somebody missed. It is what a link is for: the link's job is to make the scene match the source, and an element that no longer exists in Revit no longer exists in the scene.
The problem is not the behaviour. The problem is that the decision is taken without you, at a moment you did not choose, on geometry that may be carrying a week of your work.
What actually happens
3ds Max tracks linked elements through the File Link Manager. When the source Revit file drops an element, the next reload updates the scene and strips the corresponding geometry out of it.
What leaves with the geometry is the part that costs you:
| Gone with the object | Why it matters |
|---|---|
| The materials assigned in 3ds Max | Including any V-Ray or Corona setup built on top of what came from Revit. |
| The modifier stack | Edit Poly, Unwrap UVW, anything applied after import. |
| UVW mapping | Any manual work done on top of the imported mapping. |
| The object itself | There is no undo across a reload. |
Why deletion is different from every other change
Most link behaviour is recoverable. A material that resets can be reassigned. Geometry that shifts can be checked against the model. Deletion is the one operation with no way back inside the link, because there is nothing left to inspect.
It is also the one most likely to happen for a reason that gets reversed. Design decisions are provisional. A wing gets cut on Tuesday and reinstated on Friday. The link treats both events as equally final.
The workarounds people actually use
| Workaround | What it costs |
|---|---|
Save an incremental .max before every reload | Discipline on every revision, and recovering means merging objects out of an old file by hand. |
| Detach the important objects from the link | They stop updating with the model entirely, which is usually not what you wanted. |
| Ask the BIM team to warn you before deleting | Depends on people remembering, on a deadline, across two disciplines. |
Every one of them is a habit standing in for a feature.
What the behaviour should be
The reload should stop and ask, and it should not touch the scene until it has an answer. That is the principle behind Safeguard in Levlin Bridge: deletion is the one thing it will never decide on its own.
When a pull finds elements removed in Revit, it reports what it found and waits. Nothing in 3ds Max has changed at that point, and there is no automatic mode that skips the question.
| Answer | Result |
|---|---|
| Keep | The objects stay where they are, on their own layers. Revit no longer has them; your scene still does. |
| Delete | They are removed, because you said so. |
| Set aside | They move to a frozen layer named Levlin / Deleted in Revit, still carrying their materials, UVW and modifiers. |
Set aside is the answer for the Tuesday-to-Friday case. If the element returns in Revit, the next pull returns the object to its own layer, unfrozen, with the work still on it. Nothing is re-imported and nothing is rebuilt. It is a waiting room, not a graveyard.
The full behaviour is published as reference documentation on GitHub.
Frequently asked
What happens in 3ds Max when I delete an element in Revit?
On the next reload of the link, the corresponding geometry is removed from the 3ds Max scene automatically, along with the materials, modifiers and UVW that were on it.
Can I undo it after a reload?
No. There is no undo across a reload. If the object was not saved in an earlier .max file, the work on it is gone.
Is there a setting that stops the link deleting objects?
Not in the native File Link. The link's purpose is to make the scene match the source, and removal is part of that.
What if the element comes back in Revit later?
With the native link the object is rebuilt from scratch, so the materials, modifiers and UVW that were on it before are not restored. A tool that set the object aside rather than deleting it can return it intact.
How does Levlin Bridge handle it?
It stops and asks before changing anything, offering Keep, Delete or Set aside. Set aside moves the objects to a frozen layer with their work still attached, and if the element returns in Revit the next pull returns the object to its own layer, unfrozen.
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?
- Why modifiers and UVW break when a Revit link reloads
- 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.