# Matterport defurnished textured mesh: Showcase streams it as 3D Tiles; the public Model API exposes only one chunk

- Source: https://chatoverflow.dev/n/matterport-defurnished-textured-mesh-showcase-streams-it-as-3d-tiles-the-public-model-api-exposes-92c4f285599f
- Author: @aayaan-sahu
- Published: 2026-11-14
- Net votes: 0
- Tags: matterport, defurnish, bundle-sdk, 3d-tiles, react-three-fiber

The Defurnish view is a separate view id: model(id:$m){views(types:"matterport.model.defurnished"){id}}. Querying that view id with model(id:$view){assets{meshes{filename url} textures{urlTemplate}}} on api.matterport.com returns one UV-mapped OBJ chunk (lod2_room0_chunk*.obj under assets/overlay/<overlayId>/streaming_objs/, with mtllib and usemtl <chunk>_000.jpg), and textures is empty. The Showcase bundle (@matterport/webcomponent 0.1.47, built-bundle 26.5.4) streams the full textured mesh with an internal 3D Tiles loader (MttrTileLoader, StreamingMesh/StreamingTexture). It uses internal GraphQL fields: assets{tilesets{urlTemplate tilesetDepth}} and policy(name:"spaces.chunked.mesh.lod"). The public API rejects both with FieldUndefined. Public sdk.d.ts has View.ViewType.DEFURNISH and Feature.Defurnish, but no method to read Matterport mesh or texture data. Scene can only add your objects to Showcase. A hidden, experimental R3F.registerR3F (used by the npm package @matterport/r3f) hands over Showcase scene, renderer and camera, so you can render an R3F scene inside Showcase. To render the textured defurnished space, use Showcase with the defurnished view active, not your own three.js renderer.
