NVIDIA releases four open models for driving and two-arm robot simulation
The Cosmos 3 Nano checkpoints generate sensor data and action-driven video. One keeps physics in a conventional simulator; another predicts robot scenes directly.
Loading page…
The Cosmos 3 Nano checkpoints generate sensor data and action-driven video. One keeps physics in a conventional simulator; another predicts robot scenes directly.
Listen to this story
NVIDIA’s four Cosmos 3 Nano checkpoints divide interactive simulation into specialized tasks: generating driving scenes, streaming controlled driving footage, rendering simulator-computed states, and predicting robot observations from actions. The weights are available for commercial and non-commercial use under NVIDIA’s OpenMDW1.1 license, with recipes for adapting them to new sensors and robots. They are components rather than complete simulators: physical state and runtime infrastructure remain external, and NVIDIA says their suitability for policy training and evaluation still needs to be measured.
Transfer-Auto generates synchronized video for up to 11 camera views, including fisheye, alongside LiDAR; Sim-Auto streams controlled chunks but needs a runtime and World Scenario Map renderer.
Sim-Transfer renders video from spatial controls while the simulator computes motion, contact, and authoritative physical state.
Sim-Bimanual predicts observations from actions for YAM and AgiBot two-arm robots, using either policy controls or human-operated joysticks.
NVIDIA has released four open-weight Cosmos 3 Nano models for generating driving environments and two-arm robot simulations. The checkpoints let developers create synchronized sensor data, turn simulator output into video, or predict scenes from robot actions. They provide starting points for interactive environments, not a guarantee that those environments faithfully support training or evaluation.
The downloadable checkpoints are specialized versions of the same model family: Transfer-Auto, Sim-Auto, Sim-Transfer and Sim-Bimanual. NVIDIA says their OpenMDW1.1 license permits commercial and non-commercial use under its terms. Alongside the weights, it provides post-training recipes—steps for adapting an existing model to a developer’s own sensors, environments or robot design.
Transfer-Auto handles offline synthetic driving data. NVIDIA says it generates synchronized video across up to 11 camera views, including fisheye views, and can generate color images together with LiDAR sensor data. Scene controls specify road structure and traffic motion, while text prompts guide appearance, including weather, lighting and time of day.
Sim-Auto is its streaming counterpart. It generates small, successive chunks of synchronized camera video and LiDAR, using its generated history and updated driving controls. That allows new controls to influence an unfolding sequence. Closing the loop still requires a simulation runtime and a World Scenario Map renderer to translate driving inputs into updated controls; the checkpoint does not supply that entire system.
The other two checkpoints split the simulation task differently. One renders a state computed elsewhere. The other generates the next observation directly from actions and the current scene.
Streaming generation builds each short segment from prompts, controls and earlier generated footage. An attention cache retains information for the next prediction, while the model blocks access to future target observations. Smaller chunks let fresh controls affect generation more often, rather than waiting for a long video segment to finish.
NVIDIA’s four-stage training recipe first learns from complete recordings, then teaches chunk prediction from earlier recorded observations. A distillation stage trains a model to generate each chunk in four denoising steps, progressively refining noisy video representations. Finally, “self-forcing” trains on the model’s own generated history. That addresses a specific problem: a mispredicted object becomes context for later frames, allowing errors to compound.
Adaptation also has an order. For a new driving sensor layout or domain, NVIDIA instructs developers to adapt Transfer-Auto first, then train and distill it into Sim-Auto. For Sim-Bimanual, the listed requirements include Linux, an NVIDIA GPU, Docker and NVIDIA Container Toolkit. Its published serving setup was tested on one GB200; NVIDIA explicitly says that is not a minimum-memory specification.
Loading discussion...
Join the conversation
Explain where you would draw the line between generated images and simulated behavior.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.