Guide · what's real vs hype

MotionBricks and Unreal Engine 5: what's actually available

Searches for motion bricks unreal engine usually mean one of three things: the demo video, a plugin that doesn't exist yet, or the collision question. Here is each, straight from the official sources.

The uncut UE5 demo

NVIDIA released a 2:40 one-take UE5 demonstration covering navigation and object-scene interaction at industry-game scope. Its headline is also its technical claim: every motion comes from the neural model — no foot-locking, no blending, no collision detection, no hand-authored transitions. The page calls it, to the authors' knowledge, the first neural model reaching that combination of quality, controllability, complexity and completeness.

Demo download (official, video only): the project page links the 4K file (~1.2 GB) — aibm_runtime_main_demo_latest_art_v3.mp4. Watch inline on nvlabs.github.io/motionbricks before downloading; that link is the only legitimate source.
MotionBricks overview figure: unified control across animation and robotics, from the official project page
Official overview — unified control across animation and robotics. Hosted by NVIDIA, not mirrored.

Is there a UE5 plugin? Not in the preview

The public preview (2026-04-27) ships a Python runtime with a MuJoCo-based interactive G1 demo plus training code. Engine-side material — the smart-primitive authoring you see in the demo being wired "plug-and-play like stacking bricks" inside UE5 — is shown in the paper and page, but no public UE5 plugin is in the repository. The official roadmap states a full release (model embedded in GR00T WBC's robotics formulation, complete training pipeline) targeted approximately one month out from the preview. Treat any third-party "MotionBricks UE5 plugin download" as unverified until it points back to the NVIDIA repo.

Integrating today, honestly

"Can I interact with collision on UE5?"

This search gets asked backwards. The demo's objects (sword pickup, bench jump, sitting) are driven by smart objects: proxy keyframes that specify the interaction, and the backbone synthesizes approach, contact and follow-through with natural variation across runs. There is no collision solver to toggle — the paper's position is that contact behavior is learned, not simulated. If your game needs true physics response (impacts, ragdolls, destructibles), MotionBricks is a motion generator, not a physics engine.

Smart objects in motion (official GIFs)

G1-style character picking up a sword, generated interaction
Pick up sword — official GIF
Character jumping over a bench with natural approach and landing
Jump over bench — official GIF
Character sitting on an object generated by smart-object proxy keyframes
Sitting — official GIF
Interactive authoring workflow for smart objects
Interactive authoring — official GIF

UE5 FAQ

Is there a MotionBricks UE5 demo download?
NVIDIA publishes the uncut 2:40 UE5 demo video (4K, ~1.2 GB) as a direct download on the official project page — that is the demo people mean by motionbricks ue5 demo download. It is a video of the runtime in action, not an engine package. The MotionBricks preview code itself lives in the GR00T-WholeBodyControl GitHub repository (MuJoCo runtime); no UE5 plugin is in the public preview, and the full robotics/engine release was targeted roughly one month after the 2026-04-27 preview in the official roadmap.
Can I interact with collision in the UE5 demo?
No collision detection is used at all — that is the official selling point. The project page states every motion is generated by neural networks with no foot-locking, no blending, no collision detection and no hand-authored transitions. Object interaction is handled by smart-object proxy keyframes: the backbone fills in approach, contact and follow-through rather than a physics solver resolving contacts.
How does MotionBricks work with Unreal Engine?
In NVIDIA's authoring workflow, smart-object behaviors are set up end-to-end inside UE5 — proxy keyframes on scene objects, no animation-graph wiring. For third-party integration, what is public today is the Python/MuJoCo runtime and model layer; bridging to UE5 means consuming generated motion streams yourself. Expect the official path to arrive with the full release tracked in the README roadmap.
Where can I use MotionBricks assets in my own Unreal project?
You cannot take the demo's assets: the UE5 footage, its meshes and environments are NVIDIA's. Source code is Apache 2.0 and weights fall under the NVIDIA Open Model License; anything you integrate from the public repository follows those terms, which this unofficial guide summarizes but does not replace.