LNK2019 unresolved external symbol _imp__GetCOREInterface12 when building 3ds Max SDK plug‑in

Question

Determine whether to link against the static maxapi.lib import library or the DLL import library when configuring a repeatable development environment for Autodesk 3ds Max plug‑in projects that use the SDK.
The SDK version must exactly match the target 3ds Max release, the platform toolset must be compatible with the Visual Studio version, and the build must target x64. Static linking removes the need for the runtime DLL but increases the plug‑in’s file size and can lead to load‑time failures if the plug‑in is executed with a different 3ds Max version. DLL import keeps the plug‑in smaller but requires the exact 3ds Max runtime to be present on every machine that runs the plug‑in.
Which linking strategy provides the most reproducible builds across developer workstations? How does static linking affect plug‑in size and the risk of version‑specific load failures? What are the runtime compatibility implications of relying on the DLL import library?

Tasadduq Burney · Answer

Answer
For a 3ds Max plug-in the SDK ships only an import library (maxapi.lib). There is no supported static Max API library, so static linking is not an option. The plug-in must be linked against maxapi.lib, which resolves at load time to maxapi.dll that is part of the installed 3ds Max application.
Why the LNK2019 error appears

Missing maxapi.lib in Additional Dependencies.
Architecture mismatch (building x86 while the SDK and Max runtime are 64-bit or vice-versa).
Wrong SDK path or toolset that prevents the linker from finding the import library.
Using a different Max version than the one the SDK targets.

Reproducible build strategy

Install the exact 3ds Max release that the SDK targets (e.g., 3ds Max 2026 with the 2026 SDK).
In Visual Studio project properties:

Set Configuration to Release (or Debug) and Platform to x64.
Under Linker → General → Additional Library Directories, add the path to the SDK's lib folder.
Under Linker → Input → Additional Dependencies, add maxapi.lib.

Build the plug-in and verify that the resulting .x64.dll loads in the same 3ds Max instance.
Optionally, use a build script that checks the SDK version, toolset, and library paths to enforce consistency across all developer machines.

Runtime implications

The plug-in depends on maxapi.dll at runtime; it will load only when the matching Max executable is present.
If a different Max version is installed, the plug-in may fail to load or crash due to ABI changes; Autodesk does not guarantee binary compatibility across releases.
Because the import library is only a thin wrapper, the plug-in stays small; the bulk of the API code resides in the Max runtime DLL.

Missing diagnostic detail
To fine-tune the recommendation, it would help to know the exact Visual Studio version, platform toolset, and whether any third-party libraries modify the link command. Providing those details confirms that the configuration matches the SDK and that the import library is correctly referenced.

LNK2019 unresolved external symbol _imp__GetCOREInterface12 when building 3ds Max SDK plug‑in

1 answer

Answer

Why the LNK2019 error appears

Reproducible build strategy

Runtime implications

Missing diagnostic detail

Your perspective belongs here.

0 question comments