如何加载带纹理的FBX 6100及FBX SDK 2011格式3D文件？

Absolutely, there are practical ways to handle these legacy FBX formats—since three.js only supports FBX 7100 and above, here are your most reliable options:

1. Convert to a Supported Format (Simplest Approach) #

This is the go-to solution for most cases, as it avoids dealing with low-level format parsing:

• Blender: It has robust support for importing old FBX versions (including 6100 and SDK 2011). Import your file, verify that textures are correctly linked (check the Shader Editor/UV Editor to confirm), then export to a three.js-friendly format like glTF/GLB (preferred for web performance) or FBX 7100+. Blender will handle texture packing and format conversion seamlessly.
• Autodesk FBX Converter: A dedicated tool from Autodesk designed specifically for FBX version conversion. It can batch-convert old FBX files to 7100+ while preserving texture mappings and mesh data. Just load your source files, select the target FBX version, and export—no extra 3D editing needed.

2. Use a JavaScript Library That Supports Legacy FBX #

If you need to handle conversion directly in the browser, consider these libraries:

• Assimp.js: A WebAssembly port of the Open Asset Import Library (Assimp), which supports a wide range of legacy 3D formats including old FBX. You can use it to parse the FBX 6100/2011 file directly in the browser, then map the parsed mesh, material, and texture data to three.js Object3D, MeshStandardMaterial, and Texture objects. The library handles most texture types (diffuse, specular, etc.) and UV mappings out of the box.
• Legacy Three.js FBXLoader Forks: Earlier versions of three.js (pre-r100) included an FBXLoader that supported older FBX formats. You can find community-maintained forks of these loaders, or pull the old loader code from the three.js GitHub archive and adapt it to work with modern three.js versions. Note that this may require updating some API calls to match current three.js conventions.

3. Backend Conversion Pipeline #

If front-end parsing is too resource-heavy, set up a backend conversion step:

• Use tools like Assimp (via Python/C++ bindings) or the Autodesk FBX SDK 2011 itself to convert old FBX files to glTF or FBX 7100+ on your server. You can write a simple script to process files on upload or on-demand, then serve the converted files to your three.js application. This approach offloads the heavy lifting from the client and ensures consistent conversion results.

Key Notes to Avoid Issues #

• Always verify texture paths after conversion: Legacy FBX files often use relative paths, so make sure texture files are in the correct location relative to the converted model file.
• Check material compatibility: Old FBX materials may use deprecated properties (like specular maps in older shading models). You may need to adjust material settings in three.js to match the original look.

内容的提问来源于stack exchange，提问作者Nguyễn Minh Vương