SimReady Conform FET_003_PHYSX
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_003_PHYSX. It repairs or stages rigid body physics (physx) conformance without drifting into another runtime contract.
Default to FET_003_PHYSX@0.4.0 when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different FET_###_RUNTIME feature, switch to that feature's matching skill before editing.
Source of Truth
Before changing an asset or package, read:
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.1.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.2.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.3.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.4.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX.md
Treat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.
Feature Versions
| Version |
Dependencies |
Requirements |
0.1.0 |
FET_003_STANDARD@0.1.0 |
COL.001 |
0.2.0 |
None |
RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.006, RB.007, RB.009, RB.010, PHYSX.COL.001, PHYSX.COL.002 |
0.3.0 |
None |
RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.007, RB.009, RB.010, PHYSX.COL.001, PHYSX.COL.002 |
0.4.0 |
None |
RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.007, RB.009, RB.010, PHYSX.COL.001, PHYSX.COL.002 |
Feature Adapter
When the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data first (via the workspace upgrade command; see nv_core/sr_specs/docs/guides/feature_adapters/feature_adapters.md), then repair only the residual requirements below.
| Adapter module |
Adapter |
Transition |
Authors |
nv_core/cip_specs/asset_handler_modules/neutral_to_physx |
rigid_body_neutral_to_prop_physx |
FET_003_STANDARD@0.1.0 -> FET_003_PHYSX@0.1.0 |
Mesh extents on all meshes. |
- The adapter runs on a staged output stage and never creates geometry; it only annotates existing prims. Ensure colliders/rigid bodies already exist.
- It reaches
FET_003_PHYSX@0.1.0 only. The default @4 (and @2/@3) adds RB.* rigid-body and PHYSX.COL.001/PHYSX.COL.002 requirements that the adapter does not author; repair those manually per the Workflow below.
Workflow
- Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.
- Load the selected
FET_003_PHYSX manifest and the feature markdown before editing.
- Load requirement docs linked from the feature markdown for every reported failing requirement.
- Create or use a staged output location unless the user explicitly asks for in-place edits.
- Repair only the requirements listed by the selected
FET_003_PHYSX manifest and its dependencies.
- Rerun the same profile gate or the narrowest available feature/capability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.
- Summarize the selected
FET_003_PHYSX version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Repair the selected PhysX rigid-body feature and use PhysX-only collider schema only when the manifest allows it.
- Keep multibody joint and articulation work in FET_004_PHYSX or related robot features.
- Record whether runtime or validator evidence was available for PhysX collider behavior.
Report Fields
| Field |
Meaning |
feature |
Exact feature ID and version, for example FET_003_PHYSX@0.4.0. |
input |
Source asset, package root, or package definition inspected. |
output |
Staged output path, or in-place only when explicitly requested. |
requirements_repaired |
Requirement IDs repaired in this pass. |
validation |
Command or inspection used to verify this exact feature. |
status |
passed, failed, skipped, or blocked. |
next_step |
The next exact feature skill or user/runtime evidence needed. |
1---2name: simready-foundation-conform-fet-003-physx3description: "Use for repairing exact FET_003_PHYSX SimReady conformance for rigid body physics (physx) conformance. Use when a profile, validation report, or user request names FET_003_PHYSX; default to version `0.4.0` unless a profile or report pins another version."4license: Apache-2.05metadata:6 source: https://skillmd.com/skills/nvidia/simready-foundation-conform-fet-003-physx7 author: "Shaad Boochoon <sboochoon@nvidia.com>"8 tags:9 - simready10 - conformance11 - physx12---1314# SimReady Conform FET_003_PHYSX1516## Purpose1718Use this exact feature skill when the selected profile, validation report, or user request names `FET_003_PHYSX`. It repairs or stages rigid body physics (physx) conformance without drifting into another runtime contract.1920Default to `FET_003_PHYSX@0.4.0` when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different `FET_###_RUNTIME` feature, switch to that feature's matching skill before editing.2122## Source of Truth2324Before changing an asset or package, read:2526- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.1.0.json`27- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.2.0.json`28- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.3.0.json`29- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX-0.4.0.json`30- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_PHYSX.md`3132Treat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.3334## Feature Versions3536| Version | Dependencies | Requirements |37|---|---|---|38| `0.1.0` | FET_003_STANDARD@0.1.0 | `COL.001` |39| `0.2.0` | None | `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.006`, `RB.007`, `RB.009`, `RB.010`, `PHYSX.COL.001`, `PHYSX.COL.002` |40| `0.3.0` | None | `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.007`, `RB.009`, `RB.010`, `PHYSX.COL.001`, `PHYSX.COL.002` |41| `0.4.0` | None | `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.007`, `RB.009`, `RB.010`, `PHYSX.COL.001`, `PHYSX.COL.002` |4243## Feature Adapter4445When the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data first (via the `workspace upgrade` command; see `nv_core/sr_specs/docs/guides/feature_adapters/feature_adapters.md`), then repair only the residual requirements below.4647| Adapter module | Adapter | Transition | Authors |48|---|---|---|---|49| `nv_core/cip_specs/asset_handler_modules/neutral_to_physx` | `rigid_body_neutral_to_prop_physx` | `FET_003_STANDARD@0.1.0` -> `FET_003_PHYSX@0.1.0` | Mesh extents on all meshes. |5051- The adapter runs on a staged output stage and never creates geometry; it only annotates existing prims. Ensure colliders/rigid bodies already exist.52- It reaches `FET_003_PHYSX@0.1.0` only. The default `@4` (and `@2`/`@3`) adds `RB.*` rigid-body and `PHYSX.COL.001`/`PHYSX.COL.002` requirements that the adapter does not author; repair those manually per the Workflow below.5354## Workflow55561. Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.572. Load the selected `FET_003_PHYSX` manifest and the feature markdown before editing.583. Load requirement docs linked from the feature markdown for every reported failing requirement.594. Create or use a staged output location unless the user explicitly asks for in-place edits.605. Repair only the requirements listed by the selected `FET_003_PHYSX` manifest and its dependencies.616. Rerun the same profile gate or the narrowest available feature/capability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.627. Summarize the selected `FET_003_PHYSX` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.6364## Feature Guidance6566- Repair the selected PhysX rigid-body feature and use PhysX-only collider schema only when the manifest allows it.67- Keep multibody joint and articulation work in FET_004_PHYSX or related robot features.68- Record whether runtime or validator evidence was available for PhysX collider behavior.6970## Report Fields7172| Field | Meaning |73|---|---|74| `feature` | Exact feature ID and version, for example `FET_003_PHYSX@0.4.0`. |75| `input` | Source asset, package root, or package definition inspected. |76| `output` | Staged output path, or `in-place` only when explicitly requested. |77| `requirements_repaired` | Requirement IDs repaired in this pass. |78| `validation` | Command or inspection used to verify this exact feature. |79| `status` | `passed`, `failed`, `skipped`, or `blocked`. |80| `next_step` | The next exact feature skill or user/runtime evidence needed. |