How to relink 3ds Max files without opening them

You buy an asset pack from 3dsky. Drop the .max file into your scene. Half the textures show up missing.

The paths inside that file point to something like D:\3D\Projects\evermotion_archmodels\textures\fabric_diffuse.jpg. That's wherever the asset's creator had it saved when they hit save. It's not where you keep textures. 3ds Max can't find any of the bitmaps.

Every studio has its own way of dealing with this. Most of them involve a relink script: somebody on the team wrote it years ago, somebody else tweaked it, and it sits in a _pipeline\scripts folder being passed around. The script does the job. It also has one fundamental problem: it needs the file open in 3ds Max before it can touch the paths.

Why opening the file is the expensive part

A clean asset opens quickly. A heavy archviz scene, with V-Ray or Corona proxies waiting to initialise or linked XRefs to resolve, can take minutes to load before the script has done anything. Multiply that by a forty-asset pack and you have half a day of "3ds Max is opening", followed by Asset Tracking dialogs, save cycles and the occasional crash on a particularly bloated scene.

Batch mode helps, but it still opens each scene before relinking, so the load is still the bottleneck. And when the script runs inside your working scene after a merge, the fix never reaches the source file. The same asset arrives broken again next time and you relink it again.

Relinking without opening Max

You shouldn't need to open every scene just to fix its paths. SAM does it for you:

• It indexes your library folders and finds the missing maps in each .max file, without you opening them one by one.
• You see every missing map across the whole pack in one place instead of one scene at a time.
• You point SAM at where your textures actually live, and it fixes the paths in the files themselves, so the fix sticks.

I've run both approaches side by side. On a single small file the in-Max script can win, because indexing a folder has its own overhead. Across a whole pack the gap is large, and you don't have to babysit it. I haven't timed it carefully enough yet to give you a number, so I won't.

The one limit you should know about

If your library lives at a longer path than the creator's, the new path may not fit in the file. SAM then writes just the filename and warns you. 3ds Max then resolves the filename against its bitmap search paths when the file next opens. The texture isn't lost, but you should know it happened, and SAM tells you.

Once the maps resolve

Because relinking is part of the library rather than a separate script, a fixed asset is ready to use straight away. Find it by name, tag or a reference image, then drag it from SAM into the 3ds Max viewport.

When this isn't worth it

If you already have a relink workflow that works for your studio, whether that's Connecter, a project manager or the senior artist's in-house script, and your typical project is a handful of files at a time, the time saved on relinking alone might not justify swapping. The case gets stronger when you buy packs often, because the pain is specific to purchased assets and inherited files.

The other case where this matters less: scenes you authored yourself with sensible relative paths from the start. If you rarely buy packs and every scene starts clean, the missing-maps problem barely exists for you, and neither does the case for a dedicated relink tool.

The underlying point isn't which tool to install. It's whether the operation you're doing requires 3ds Max at all. Relinking doesn't. Reading dependencies doesn't. Most of the missing-maps pain in ArchViz comes from doing file-management operations through a UI built for scene editing.

Further reading: 3dsky downloads without the unzipping and renaming · SAM vs Connecter: which asset manager fits a 3ds Max artist?