OVRTX sensor capture
Use the public client in addon/ and its tests. Sensor identity is
the USD product path, not a Blender object name or output filename.
- Run the focused
tests/test_ovrtx_runtime_client.py and
tests/test_ovrtx_session.py controls, then inspect a compatible native
probe under scripts/ before adapting it.
- Supply an explicit fixture, worker, native-client path, sensor paths, matching
RenderVar paths, dimensions, time, and caller-owned output JSON.
- Require successful worker start, simulation creation with every requested
sensor, one bounded sample step, exact per-RenderVar reads, decoded frames,
finite dimensions/data, deletion, and shutdown.
- Run
test_ovrtx_runtime_client.py and test_ovrtx_session.py; retain tests
for deduplication, changed-sensor session identity, selected-product routing,
iterator pages, and terminal errors.
The current public probes cover LdrColor camera products. For depth,
semantic, LiDAR, or another sensor schema, first probe native capabilities and
then use the corresponding extension skill. Do not synthesize output from mesh
sampling or postprocessing while labeling it native sensor readback.
1---2name: ovrtx-sensor-capture3description: Customize and validate OVRTX sensor declaration, selection, stepping, and native readback for one or multiple render products. Use when developers add camera-like sensors or debug sensor identity and output routing in the add-on. This skill probes capabilities and does not claim every sensor family is already implemented.4---56# OVRTX sensor capture78Use the public client in `addon/` and its tests. Sensor identity is9the USD product path, not a Blender object name or output filename.10111. Run the focused `tests/test_ovrtx_runtime_client.py` and12 `tests/test_ovrtx_session.py` controls, then inspect a compatible native13 probe under `scripts/` before adapting it.142. Supply an explicit fixture, worker, native-client path, sensor paths, matching15 RenderVar paths, dimensions, time, and caller-owned output JSON.163. Require successful worker start, simulation creation with every requested17 sensor, one bounded sample step, exact per-RenderVar reads, decoded frames,18 finite dimensions/data, deletion, and shutdown.194. Run `test_ovrtx_runtime_client.py` and `test_ovrtx_session.py`; retain tests20 for deduplication, changed-sensor session identity, selected-product routing,21 iterator pages, and terminal errors.2223The current public probes cover LdrColor camera products. For depth,24semantic, LiDAR, or another sensor schema, first probe native capabilities and25then use the corresponding extension skill. Do not synthesize output from mesh26sampling or postprocessing while labeling it native sensor readback.
NVIDIA-Omniverse