NVIDIA pushes 'Physical AI'
NVIDIA is leaning into robotics as “physical AI,” promoting Omniverse libraries to tie simulation, perception and deployment into one workflow and positioning its stack as the standard tooling for robot development. The company highlighted robot‑learning and foundation‑model research for National Robotics Week and says teams can now integrate physical‑AI capabilities into existing apps using Omniverse libraries. This doubles as a labour‑market signal: employers will increasingly expect engineers who can bridge simulation and real‑world validation rather than treat them as separate tasks. ( )
Robots are hard to train for the same reason self-driving cars are hard to test: you cannot crash a real machine into every possible shelf, stair, puddle, and person just to see what happens. NVIDIA’s answer is to do that work first in software, then carry the results into the real machine. (blogs.nvidia.com) That software-first step is called simulation, and it works like a flight simulator for robots. A team builds a digital copy of a warehouse, factory, or field, then lets the robot practice there before it ever touches the floor. (blogs.nvidia.com) The catch is that a fake world is only useful if it behaves enough like the real one. NVIDIA has spent years pushing Omniverse as the place where lighting, materials, motion, and sensor data can be modeled closely enough that robot training does not have to start from zero in the real world. (developer.nvidia.com) This week NVIDIA wrapped that pitch in a bigger label: “physical artificial intelligence.” In the company’s wording, that means artificial intelligence systems that can perceive, reason, and act in simulated environments tied to real physical tasks. (developer.nvidia.com) The new part is not just the slogan. NVIDIA said on April 8, 2026 that software teams can now plug Omniverse pieces directly into existing products instead of adopting an entire new application stack. (developer.nvidia.com) That matters because most industrial companies already have their own tools for design, planning, and operations. NVIDIA is offering libraries for rendering, physics, and data storage so those companies can add robot simulation and digital-twin features without rebuilding everything around NVIDIA from scratch. (developer.nvidia.com) One library, called ovrtx, is meant to simulate what robot sensors see. NVIDIA says it can bring real-time path tracing and sensor simulation into an existing app, which is useful for perception training and for generating synthetic data when real camera footage is scarce or expensive. (developer.nvidia.com) Another library, called ovphysx, handles physics. That is the part that decides whether a box slips, a gripper bounces, or a wheeled robot tips, and NVIDIA is selling it as a hardware-accelerated way to run those tests inside Universal Scene Description, the scene format known as OpenUSD. (developer.nvidia.com) NVIDIA is also tying this push to foundation models for robots, which are large base models trained to handle broad classes of physical tasks instead of one narrow motion. In its National Robotics Week post, the company grouped robot learning, simulation, and foundation models as the three ingredients speeding up the jump from virtual training to real deployment. (blogs.nvidia.com) There is already an early customer story attached to the pitch. On March 19, 2026, NVIDIA said ABB Robotics was using Omniverse libraries inside RobotStudio, and NVIDIA claimed the setup could close the simulation-to-real gap with 99 percent accuracy in pilots ahead of a 2026 release. (blogs.nvidia.com) So the real news is not that NVIDIA likes robots. It is that NVIDIA wants the standard robot workflow to run through its tools from virtual training to sensor testing to factory deployment, which would make “simulation plus real-world validation” one job instead of two separate specialties. (blogs.nvidia.com, developer.nvidia.com)
