この記事はまだ日本語に翻訳されていないため、英語の原文を表示しています。

More ways to bring your 3D models into AR Works

読了時間:3分

An OBJ file could fail to import because one of its texture images was missing or unreadable. You would see an error about the whole model, even when the shape itself was fine.

We've changed how AR Works imports models. Alongside support for more file formats, the importer now preserves material colours and supported textures and tells you when something could not come across.

More formats to work with

You can now import GLB, glTF, FBX, OBJ, DAE, STL, PLY, 3DS, 3MF, AMF, WRL, VRML and VTK, as well as KMZ archives containing a Collada model. The same formats work in a project's Assets panel and in your Asset Library.

Files that need conversion become a GLB in your browser before they are uploaded. That gives the editor and the AR viewer a model they can both use, without an extra conversion step for you. Embedded animations come along where the source format and importer support them. Draco- and Meshopt-compressed models, and KTX2 textures, are decoded during import.

Keeping the materials

Colours and supported texture maps are carried into the converted model, including textures supplied as TGA or DDS files. Where possible, separate transparency and bump maps are converted into materials that work in AR.

A missing texture now produces a warning rather than rejecting an otherwise usable model. In the project import preview, you can see which resources need attention and decide whether to continue or cancel and add the missing files. The Asset Library also shows material warnings beside completed uploads.

The importer has also become better at finding those files when their references contain spaces, quoted names or paths from the computer where the model was made.

Import the files together

In your project, open Assets → Import → From disk. Select the model and any files it needs in the same import:

  • For an OBJ, include its MTL file and texture images. The MTL describes the materials; it does not usually contain the images themselves.
  • For a glTF, include its BIN file and texture images when these are supplied separately.
  • For FBX, DAE and other models with separate textures, include those image files too.

The preview lets you turn the model around and check its materials before importing. It also lists any embedded animations and plays the first one. If a warning names a missing image, cancel, find that image in the original download, and select it with the model when you try again.

A few limits still matter

A file extension does not guarantee that every variation of that format can be read. Native project files such as BLEND and MAX still need to be exported from their original application, preferably as GLB. Materials built with procedural nodes may need their appearance baked into texture images first. STL carries shape, so it cannot bring image textures with it. PLY imports need polygon faces; point-cloud PLY files are not supported.

If a model failed to import before, try it again with its companion files selected. The asset import guide covers the steps, and the preview will show you what made it through.

AR Worksを無料で試す

ブラウザで、はじめての拡張現実体験を作ってみましょう。コードも、アプリのインストールも不要です。

ブログのほかの記事