skills.rest
NVIDIA-Omniverse
NVIDIA-OmniverseOFFICIAL
Explore all skills by this author →
Website𝕏@nvidiaomniverseGitHub

nonvisual-materials

Assign nonvisual material semantics to USD materials for sensor simulation.

201|25|Updated Dec 18, 2025
Search Tags:#usd#radar#lidar#acoustic#nonvisual-materials#sensor-semantics#material-id
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/ovrtx --skill nonvisual-materials
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nonvisual-materials
Source: https://github.com/NVIDIA-Omniverse/ovrtx/tree/main/.agents/skills/nonvisual-materials
Command: npx skills add https://github.com/NVIDIA-Omniverse/ovrtx --skill nonvisual-materials

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoring non-visual material labels for sensor simulation. Use when user asks to assign lidar/radar/acoustic material semantics, choose nonvisual base materials, coatings, or attributes, debug material IDs, or bind sensor-facing USD materials.

Core Features & Use Cases

  • Nonvisual material labeling on Material prims to drive sensor semantics.
  • Supports base materials, coatings, and attributes for lidar, radar, and acoustic surfaces.
  • Use cases include debugging MaterialId mappings and binding sensor-facing USD materials.

Quick Start

Annotate material prims in your USD scene with nonvisual labels to define sensor semantics.

Frequently Asked Questions about nonvisual-materials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assign nonvisual material semantics to USD geometry for lidar and radar sensors?▼

You can assign nonvisual material semantics by annotating material prims in your USD scene with specific base materials, coatings, and attributes to drive sensor returns and debugging behavior.

What are nonvisual materials used for in sensor simulation?▼

Nonvisual materials drive sensor semantics for lidar, radar, and acoustic sensors by providing material IDs that influence behavior and scene realism across varied objects in simulation.

How do I debug material ID mappings for acoustic and radar sensors?▼

Debug material ID mappings by validating the exact base material values, optional coatings, and attributes bound to your sensor-facing USD materials using the provided source snippets and examples.

Can I add coatings and attributes on top of a base nonvisual material for sensor returns?▼

Yes, you can define optional coatings and attributes alongside enforced exact base material values on USD material prims to fine-tune lidar, radar, and acoustic sensor simulation behaviors.

Does this workflow require specific dependencies to bind sensor-facing USD materials?▼

No specific dependencies are required to bind sensor-facing USD materials, as the workflow operates directly on material prims within your existing USD scene to establish sensor semantics.

When do I need to use nonvisual material labels instead of standard visual materials?▼

You need nonvisual material labels when lidar, radar, or acoustic sensors require material IDs to accurately influence behavior and scene realism, bypassing standard visual material properties.

Related Skills

Explore More Software Engineering Skills→
PubCyBerryPubCyBerry

nonvisual-materials

Assign non-visual material labels and attributes to USD assets for sensor simulation.

Community
Intermediate
PubCyBerryPubCyBerry

configuring-radar-sensors

Configure OmniRadar sensor prims and point cloud outputs for simulation scenes.

Community
Intermediate
PubCyBerryPubCyBerry

reading-sensor-pointclouds

Map and read lidar or radar PointCloud tensors for sensor data processing.

Community
Intermediate
PubCyBerryPubCyBerry

binding-materials

Assign and update material bindings on USD geometry prims.

Community
Intermediate