Native Physics API Access
Native physics APIs are backend-specific escape hatches. They can bypass Isaac Lab’s buffering, validation, ordering, and lifecycle management. Use the unified asset and sensor APIs unless an engine-native capability or a lower-overhead data path is required.
Choose an access level
Use native access only when the unified APIs do not provide a capability or data path that the workload needs. Keep it close to the component that owns the simulation state. For the portable API boundary and backend lifecycle, see Backend architecture.
- Use the unified Isaac Lab data and write APIs for portable task code.
- Reuse an Isaac Lab-owned native handle when its selection already matches.
- Create raw engine access only for a selection or capability that the owning Isaac Lab object does not expose.
Ownership and synchronization
Isaac Lab also reads the native state and model for you when feeding renderers and visualizers. See scene_data_providers for that read path.
Backend-specific guides
- PhysX: Tensor views and native access
- Newton: Native access
- OvPhysX: Native access