NVIDIA Cosmos 3 Open Models Stream 11-Camera Driving Worlds
In this article
NVIDIA has added four open-weight checkpoints to Cosmos 3 for interactive world simulation: Cosmos3-Nano-Transfer-Auto, Cosmos3-Nano-Sim-Auto, Cosmos3-Nano-Sim-Transfer, and Cosmos3-Nano-Sim-Bimanual. Published on Hugging Face on November 5, 2026, all four are post-trained examples of Cosmos 3 Nano with 16B trainable parameters, available under OpenMDW1.1 terms for commercial and non-commercial use. NVIDIA positions them as action- and control-conditioned next-observation generators, not generic video models.
| Checkpoint | Conditioning inputs | Generated output | Target use |
|---|---|---|---|
| Cosmos3-Nano-Transfer-Auto | Per-camera WSM controls, text prompts, optional initial RGB, optional HD-map range maps | Synchronized video across up to 11 cameras; joint RGB–LiDAR | Offline synthetic driving data and domain adaptation |
| Cosmos3-Nano-Sim-Auto | Per-camera captions, synchronized WSM controls, updated driving controls, HD-map range controls | Synchronized camera video and LiDAR chunks | Streaming interactive driving rollouts |
| Cosmos3-Nano-Sim-Transfer | Depth, segmentation, edges, blur controls from a simulator; text prompt | RGB video frames | Render colors while physics stays in simulator |
| Cosmos3-Nano-Sim-Bimanual | Initial image, robot or camera actions; 59 action values padded to 64 | Next observation video | Two-arm YAM and AgiBot simulation |
The autonomous-driving checkpoints split the work. Transfer-Auto is bidirectional, generating synchronized video across up to 11 camera views, including fisheyes, and joint RGB–LiDAR output. Sim-Auto is the causally distilled streaming variant, producing synchronized camera and LiDAR chunks in a few denoising steps. NVIDIA notes that closed-loop use of Sim-Auto still requires an external simulation runtime and WSM renderer to update controls from driving policy inputs.
Sim-Transfer turns a simulator’s depth, segmentation, edge, and blur controls plus a text prompt into RGB video frames while physics and ground-truth state stay in the simulator. Sim-Bimanual predicts next-observation video from an initial image and robot or camera actions, supporting two-arm YAM and AgiBot embodiments. Its mixed-action schema defines coordinate frames, rotations, gripper calibration, validity masks, and control domains, with 59 control values padded to 64 during training.
Cosmos 3 uses a Mixture-of-Transformers backbone that connects text-processing and visual-generation networks through attention. The generator predicts each short segment from the prompt, available controls, and generated history, then denoises noisy compressed video latents into a segment. After the initial image, each latent time step represents four RGB frames; the transfer checkpoint predicts one latent step per chunk, and the optimized bimanual setup in the technical report predicts two. Temporal-causal attention blocks future observations, and a key/value cache carries attention state forward.
The four-stage recipe moves from full clips to streaming. Stage 0 is bidirectional adaptation. Stage 1 uses teacher forcing with clean answers and future targets masked. Stage 2 consistency distillation trains a student with a frozen teacher to generate each chunk in four denoising steps. Stage 3 self-forcing trains on the student’s generated history using a frozen teacher and auxiliary score model. NVIDIA says the final stage matters because a slightly mispredicted object becomes context for later frames, so errors can compound.
All recipes start from Cosmos3-Nano or compatible base weights. Transfer-Auto can be post-trained on a developer’s own driving data to match a sensor rig and domain, then undergo causal training and few-step distillation into a streaming Sim-Auto variant. Sim-Transfer and Sim-Bimanual have separate environment and embodiment adaptation paths. NVIDIA instructs users to keep full training checkpoints because exported inference weights omit optimizer and other training state. The published vLLM-Omni setup was tested on one GB200, which NVIDIA says is not a minimum-memory specification. Runtime requirements are Linux, an NVIDIA GPU, Docker, and NVIDIA Container Toolkit. The blog does not list pricing for the checkpoints.
AI Mastery analysis
The practical burden is in control contracts. Transfer-Auto expects per-camera WSM controls and HD-map range maps for LiDAR; Sim-Bimanual requires coordinate frames, rotations, gripper calibration, validity masks, and control domains. Teams adopting these checkpoints must produce exactly those signals or post-train first.
NVIDIA states that measuring where the models faithfully support policy learning and evaluation remains open work. No third-party success rates, policy-training improvements, or sim-to-real transfer metrics ship with this release, so the checkpoints are an engineering substrate rather than a proven benchmark. The streaming recipe attacks compound error through self-forcing, but the blog reports no independent held-out episode evaluation.
The release fits a pattern AI Mastery has tracked: pipeline architecture, not better model weights, drives AI gains. Sim-Auto needs an external simulation runtime and WSM renderer; Sim-Transfer depends on a simulator for physics and ground truth. The single-GB200 test note leaves real-time robot-loop feasibility as an integration question. Open-weight world models are becoming actionable artifacts for embodied AI, but their practical value will be decided by community adaptation and independent downstream policy measurement, not vendor demo video.
Sources
Frequently asked questions
What are the four NVIDIA Cosmos 3 checkpoints for interactive world simulation?
Cosmos3-Nano-Transfer-Auto, Cosmos3-Nano-Sim-Auto, Cosmos3-Nano-Sim-Transfer, and Cosmos3-Nano-Sim-Bimanual. NVIDIA says all four are post-trained examples of Cosmos 3 Nano with 16B trainable parameters under OpenMDW1.1.
Does Cosmos3-Nano-Sim-Auto generate LiDAR?
Yes. NVIDIA reports that it streams synchronized camera video and LiDAR in small chunks using generated history and updated driving controls. LiDAR output requires aligned HD-map range controls, and closed-loop interaction needs an external simulation runtime and WSM renderer.
Can I adapt Cosmos3-Nano-Transfer-Auto to my own driving sensor rig?
Yes. NVIDIA positions Transfer-Auto as a foundation for post-training on your camera layout, LiDAR configuration, and target environment. The adapted model can generate offline synthetic data or undergo causal training and few-step distillation into a streaming Sim-Auto variant.
What hardware does NVIDIA list for running these Cosmos 3 checkpoints?
The published vLLM-Omni setup was tested on one GB200, which NVIDIA says is not a minimum-memory specification. Required runtime components are Linux, an NVIDIA GPU, Docker, and NVIDIA Container Toolkit.
Related Reading
Kyutai CADRE: World Models at 20 fps With Under 230 ms Lag
Kyutai's open CADRE autoencoders let world models run at 20 fps on one H100 and react in under 230 ms across robot, driving, and navigation rollouts.
NVIDIA Nemotron 3.5 Super VL: 120B MoE Runs on a Single GPU
NVIDIA's Nemotron 3.5 Super VL combines 120B total parameters with 12B active and runs the NVFP4 checkpoint on one DGX Spark, H200, or GB200.
Nemotron Scores 535.4 IOI and 30/42 IMO, Passing Gold in Both
NVIDIA reports one Nemotron family reached 535.4/600 on IOI 2026 and 30/42 on IMO 2026, above both gold thresholds.