SIMART: Decomposing Monolithic Meshes into Sim-ready Articulated Assets via MLLM

Chuanrui Zhang, Minghan Qin, Yuang Wang, Baifeng Xie, Hang Li +1 more
3/24/2026
cs.CVcs.GRcs.RO

No official code found. Best implementation: nktkt/paper-2026-03-25-simart-decomposing-monolithic-meshes-into-sim-read (0 stars, last commit 2026-03-25).

Abstract

High-quality articulated 3D assets are indispensable for embodied AI and physical simulation, yet 3D generation still focuses on static meshes, leaving a gap in "sim-ready" interactive objects. Most recent articulated object creation methods rely on multi-stage pipelines that accumulate errors across decoupled modules. Alternatively, unified MLLMs offer a single-stage path to joint static asset understanding and sim-ready asset generation. However dense voxel-based 3D tokenization yields long 3D token sequences and high memory overhead, limiting scalability to complex articulated objects. To address this, we propose SIMART, a unified MLLM framework that jointly performs part-level decomposition and kinematic prediction. By introducing a Sparse 3D VQ-VAE, SIMART reduces token counts by 70% vs. dense voxel tokens, enabling high-fidelity multi-part assemblies. SIMART achieves state-of-the-art performance on PartNet-Mobility and in-the-wild AIGC datasets, and enables physics-based robotic simulation.

View on arXivView PDF

Code Implementations(1)

Unofficial MVP implementation of SIMART: Decomposing Monolithic Meshes into Sim-ready Articulated Assets via MLLM (arXiv:2603.23386)

00PythonMar 25, 20267 months ago

Similar Papers

Cite this paper

@article{zhang2026simart,
  title  = {SIMART: Decomposing Monolithic Meshes into Sim-ready Articulated Assets via MLLM},
  author = {Chuanrui Zhang and Minghan Qin and Yuang Wang and Baifeng Xie and Hang Li and Ziwei Wang},
  year   = {2026},
  eprint = {2603.23386},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2603.23386v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2603.23386.svg)](https://codeofpaper.com/paper/2603.23386)

Discussion