NVIDIA-Omniverse/PhysX

basic-workflow

Create an ovphysx instance, attach an ovstage scene, step simulation, and clean up. Use when starting a new ovphysx project, testing basic integration, or learning the minimal workflow.

clone-environments

Clone one USD environment subtree into many runtime-only PhysX environments for RL-style batched simulation. Use when a caller needs replicated physics environments, clone API ordering, or target transform guidance.

ovphysx-output-read

Read ovphysx simulation output with the ovstage-native output-read API when results must retain ovstage identity or write back without rebuilding paths. Covers Python `PhysX.query()` + `PhysX.read()` operations and `PhysX.read_sync()`, C `ovphysx_query()` /…

ovphysx-session-write

Push caller-owned bulk control inputs and state into an ovphysx simulation with the session write API — Python `PhysX.write_sync()` or the `PhysX.query()` + `PhysX.write()` operations, C `ovphysx_write()`. Covers writing rigid-body and articulation state and…

ovphysx-usd-authoring

Author USD physics content for ovstage to populate and ovphysx to simulate (rigid bodies, colliders, mass, physics scene). Use when creating or editing .usda or USD scenes for ovstage and ovphysx, not when calling the runtime step or tensor API. Keywords USD…

tensor-bindings-cpu

Exchange CPU simulation state — poses, velocities, joint targets — as caller-owned NumPy arrays through tensor bindings. The tensor-binding CODE API is deprecated in ovphysx 0.6 in favor of the session read/write API (Python PhysX.read / PhysX.write, C…

tensor-bindings-gpu

Exchange GPU simulation state as caller-owned CUDA tensors (DLPack, GPU-to-GPU with no CPU staging) through tensor bindings. The tensor-binding CODE API is deprecated in ovphysx 0.6 in favor of the session read/write API (Python PhysX.read / PhysX.write, C…