将含OBJ/MTL/TIF的ZIP转为SVF后，Forge Viewer报Error:9求助

Hey there, let's dig into why you're seeing that Error:9 ("no viewable content available") in Forge Viewer, even though your initial translation request returned a "created" status. This error usually means the Viewer can't find any renderable geometry after translation—so let's break down the most likely fixes step by step:

1. First, Verify Your Translation Task Actually Succeeded #

The initial "created" response only means the translation job was queued, not that it completed successfully. You need to check the final status of the task using the Manifest API:

• Call GET /modelderivative/v2/designdata/{your-base64-urn}/manifest
• Look for the top-level status field:
  • If it's failed, check the errors array in the response—it'll tell you exactly what went wrong (e.g., invalid OBJ syntax, missing texture files)
  • If it's still inprogress, wait a bit longer for the translation to finish

2. Fix Your ZIP Folder Structure & File References #

OBJ/MTL/TIF combinations are picky about file paths—here's what to check:

• Keep all files in the ZIP root: Don't nest OBJ/MTL/TIF inside subfolders. Forge's translation service expects the main OBJ file to be at the root, and relative paths in the MTL to point directly to the texture.
• Double-check MTL texture paths: Open your .mtl file and look for lines like map_Kd your-texture.tif. Make sure:
  • The path is relative (no absolute paths like C:/folder/texture.tif)
  • The filename matches exactly (Forge is case-sensitive—Texture.tif vs texture.tif will break things)
• Validate your files locally: Open the OBJ + MTL + TIF in a 3D tool like Blender or MeshLab. If they don't render correctly there, they won't render in Forge either. Fix any corrupted geometry or texture references first.

3. Ensure Your Translation Request Has the Right Parameters #

When you sent the translation request, did you specify the correct output settings? For 3D OBJ models, your request payload should include:

{
  "input": {
    "urn": "your-base64-encoded-urn"
  },
  "output": {
    "formats": [
      {
        "type": "svf",
        "views": ["3d"] // This is critical—don't omit the 3d view!
      }
    ]
  }
}

If you only requested 2d views, the translation won't generate 3d geometry, which triggers Error:9.

4. Rule Out Texture Format Issues #

While Forge supports TIF textures, some compression types (like certain proprietary ones) might cause problems. Try converting your TIF to a PNG or JPG, update the MTL file to reference the new texture filename, repackage the ZIP, and re-run the translation. This often fixes hidden texture compatibility bugs.

内容的提问来源于stack exchange，提问作者Fred Coud