Community · no invented forums, no borrowed authority

Talking about MotionBricks with people

This project is young — the public preview landed 2026-04-27 — so "community" mostly means the official repo and whatever threads people have started elsewhere. Here is the honest map: what exists, who runs it, and what this site does not vouch for.

Where discussion actually happens

Official NVIDIA channel

The MotionBricks README lists one contact for questions and feedback: [email protected]. That is NVIDIA's own address for the project — reach it directly, not through this site.

GitHub issues & discussions

Bugs, setup problems, and feature requests belong in the open: NVlabs/GR00T-WholeBodyControl (MotionBricks is the motionbricks/ subproject). Issues there are the most likely path to an answer from the people building it.

Project page

nvlabs.github.io/motionbricks is the canonical demo and paper hub — its template lineage (a Nerfies-style page) tells you little; the content tells you everything.

Reddit, X, and the rest

Searching for "motionbricks" on Reddit turns up community discussion — but this site does not monitor, verify, or endorse any individual post, and it lists no specific threads because those age and get wrong. If you want the current chatter, use the search directly and treat it as third-party:

Why so few links? The most-repeated "fact" circulating in community posts is a wrong figure — 5,000 FPS where the official sources say 15,000 (see the home page correction). Third-party threads are where to find questions, not answers.

Contributing to this wiki

MotionBricks.wiki is an unofficial guide maintained by one editor. To report a stale page, a dead link, or a fact that disagrees with an official source, email [email protected].

Read this before you write: [email protected] is this site's contact address only. It is not a NVIDIA support channel and has no relationship to NVIDIA — for anything about the software itself, use [email protected] or GitHub. (Same policy as the about page.)

What gets acted on fastest: a link to the official source that contradicts something here, a reproducible setup failure with the exact command and error text, or a new dated entry from either README.

Ground rules for anything landing on this site

  1. Every fact carries an official source link. Project page, README, paper, model card, or an NVIDIA-hosted file. No source, no page.
  2. Speculation is labelled. Anything about unreleased features (Unity support, engine plugins, the roadmap window) is marked as opinion or estimate, never stated as fact.
  3. "Official support" claims are rejected. This site is unaffiliated with NVIDIA and never presents itself, or community findings, as endorsed by them. Contributions phrased as official statements get bounced.

The related projects worth knowing when a question is out of MotionBricks' scope: GEAR-SONIC for robot control, Kimodo for offline generation, BONES-SEED for the training data.