About this site
An independent guide to MotionBricks — and the rules it holds itself to
MotionBricks.wiki is a community-written documentation site for NVIDIA's MotionBricks motion framework. We are not NVIDIA, we do not speak for the researchers who built it, and we are not in a position to answer questions about it on their behalf. What we do instead: read the official materials closely and write the guide we wished existed.
Who makes this site
This guide is maintained by independent developers who spent too long untangling MotionBricks install threads and decided to write it down once. Every page footer carries the affiliation statement in full: unofficial community guide — not affiliated with, endorsed by, or sponsored by NVIDIA. MotionBricks™ and NVIDIA® are trademarks of NVIDIA Corporation. Questions about the project itself belong to its authors — [email protected] — not to us.
Methodology: how we write
- Facts are limited to named sources. Every technical claim on this site traces to one of: the official project page, the MotionBricks README, the GR00T-WholeBodyControl parent README, the arXiv paper, or the BONES-SEED dataset pages. If a source does not say it, we do not say it — and when the sources are silent we mark the gap instead of filling it (the architecture page flags exactly one such gap).
- Commands are copied, never adjusted. Every install, clone and training command appears exactly as the README writes it — comment lines included. We do not claim to have re-run them on your hardware and do not silently "improve" them.
- Numbers come from official pages only. 15,000 FPS, 2 ms, 350,000+ clips, 142,220 clips, ~288 hours, ~2.2 GB of checkpoints, the 200/80/200 ms SONIC lookaheads. No invented star counts, parameter counts or benchmarks.
- We publish our corrections. Early community posts circulated a "5,000 FPS" figure that matches no official source: Many community posts repeat a “5,000 FPS” figure. It is wrong: the official project page and README both state 15,000 FPS / 15000 FPS. Cite the paper, not the hype thread. That correction runs on every page where the stat appears, not hidden on an errata page.
- Media is linked, never mirrored. All GIFs and images on this site hotlink to NVIDIA-hosted files (media.githubusercontent.com and the project page). Nothing is re-hosted here.
Update policy
The preview release is young and the official roadmap is moving — a full training pipeline inside the GEAR-SONIC stack is "targeted for approximately one month out" per the README, counted from the 2026-04-27 announcement and stated as the project's own estimate, not a promise we echo as a deadline. We update the guide when the repository actually ships something: each dated entry below is backed by a release or news item from the official channels, and the news page tracks the same timeline as it grows. Where the roadmap slipped, we will say so rather than keep a stale date.
What this site covers
Setup
Clone, LFS, checkpoints, dependencies, first demo run.
Architecture
The three-component backbone and the smart-primitive interface.
Training
The three official training commands and dataset paths.
Styles
All 11 style keybinds with official GIFs and limits.
NVIDIA overview
What NVIDIA released, where, and under which license.
Community
Where the discussion actually happens.
Covered timeline (sourced)
- 2026-04-27 MotionBricks preview release — interactive G1 demo, pretrained checkpoints (VQVAE · pose · root), synthetic training code, motion-representation docs, GIF gallery.
- 2026-05-07 GR00T-WBC: end-to-end VLA workflow on G1 (teleop data → Isaac-GR00T N1.7 fine-tune → SONIC deployment).
- 2026-06-16 GR00T-WBC: low-latency teleoperation checkpoint (4-frame lookahead) + Isaac Teleop Setup docs.
- 2026-07-23 GR00T-WBC: SONIC v1.1 checkpoint (robot-heading-normalized, wrist-pose augmentation).
First entry from the MotionBricks README News section; the rest from GR00T-WholeBodyControl release notes. See news for links.
Contact
Found a broken link, a stale claim, or a source we should add? Reach the maintainers of this site at [email protected] — this is the guide's own address, not an NVIDIA contact, and it is not a support channel for MotionBricks bugs. For those, use the official repository and [email protected]. We read everything and correct what we get wrong.