Agent skill · nvidia
using-ovnewton
Connect the Newton physics engine to an Omniverse simulation or ovstage with ovnewton. Use when importing a populated ovstage into Newton, stepping its physics, synchronizing stage edits, or publishing simulation state for Omniverse rendering.
What it needs
About 3k tokens when loaded.
What this skill does
Using ovnewton Use ovnewton for the Newton ↔ ovstage bridge. The application owns model finalization, the solver, controls, collision handling, and the simulation loop. ovnewton reads a populated ovstage; Newton does not parse USD in this workflow. Standalone Newton simulations and generic Omniverse authoring do not need this skill. Start from the supported examples Install ovnewton in the application's environment. This workflow requires Newton 1.7 or newer, OVStage 0.3, and OVRTX 0.6 when rendering. Let its package metadata select compatible dependencies; do not replace the qualified ovstage dependency with an arbitrary build. For rendering or MuJoCo-Warp, install "ovnewton[examples]". The basic example accepts --solver mujoco or --solver vbd; VBD also supports CPU simulation. Rendering needs a supported NVIDIA GPU and its own device selection. Read the getting-started guide and adapt the basic example. For multiple robots, use the robot example. Use documentation and examples corresponding to the installed ovnewton release; repository main may describe a newer API. Construct and bind the simulation 1. Call ovnewton.registerusdschemas() before the first USD schema read. Create an ovstage.Stage() and populate the application-supplied USD with population.openusdwithdesc(stage, scenepath, ordinal=1, time=population.DEFAULTTIME, descs=(ovnewton.populationdesc(),)). Add a population.Desc(domains=PopulationDomain.RENDERING) descriptor when rendering. ovnewton.populationdesc() preserves composed schema names so unsupported physics remains detectable even without its schema plugin. Seal population with stage.advancewritefloor(1).wait() before importing. For rendering, create stages with ovstage.StageConfig selecting runtimedefaulthierarchycomputationmodel=ovstage.HierarchyComputationModel.GPUINCREMENTAL, including CPU physics with a GPU renderer. This setting is process-wide; coexisting stages must use a consistent configuration. CPU-only runs do not need this setting. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/ovnewton-usage