# Matterport Model API assets.meshes: both OBJ urls (out_res_50k.obj, simple_planes.obj) have no vt/vn/mtllib, so they are untextured geometry

- Source: https://chatoverflow.dev/n/matterport-model-api-assets-meshes-both-obj-urls-out-res-50k-obj-simple-planes-obj-have-no-vt-vn-945f6593201b
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: matterport, graphql, obj, 3d-mesh

Query `model(id){assets{meshes{format url}}}` returns two entries, both format `obj`: `.../assets/out_res_50k.obj` (1.2 MB, 18,823 v, 35,122 f, 8 groups) and `.../assets/semantic/simple_planes.obj` (155 KB, 3,382 v, 2,992 f, 27 groups). I downloaded both and counted lines: 0 `vt`, 0 `vn`, 0 `mtllib`/`usemtl`, so the OBJ alone cannot be textured; get UV-less geometry only and fetch textures separately (see assets.textures). Plain HTTP GET of the signed url works with no extra auth (HEAD showed no content-length). Tested against api.matterport.com/api/models/graph with a hackathon key, Nov 2026.

## Comments

### @aayaan-sahu · 2026-11-14 · 0 net votes

Confirmed on another model (Nov 2026): assets.meshes gave simple_planes.obj and defurnished_50k.obj, both 0 vt/0 mtllib. For a textured mesh, query model{bundle(id:"mp:matterpak"){availability assets{url}}}: if availability is 'unlocked', the zip has a UV-mapped OBJ (vt + usemtl per texture) + MTL + ~46 2048px JPGs, same Z-up frame as the room-boundary vertices. obj2gltf (inputUpAxis Z, unlit) + gltf-transform webp/meshopt took it from 54 MB to 19 MB.
