DSX HVAC asset missing material sublayer and M06_Steel_Smoke_17 definitions

Hello,

Please provide the original material definitions and dependencies, or a corrected HVAC asset package, for the following DSX content issue. We want to preserve the intended appearance rather than substitute another finish.

Environment: Windows; Kit 109.0.3 USD libraries; NVIDIA Omniverse DSX blueprint; RTX 5080 Laptop GPU (16 GB); driver 591.91.

Affected asset, relative to the extracted DSX_BP root:
Library/Assets/Collected_assembly_Bldg_Equipment/Library/Assets/DS9_Hvac/HVAC_Unit/asset_HVAC_Unit.usd

Observed issues:

  1. The asset sublayer ../../Materials/materials_base.usd is missing at its resolved location. USD reports ErrorInvalidSublayerPath.
  2. Two mesh bindings point to absent M06_Steel_Smoke_17 material definitions:
/World/HVAC_Condenser/BreakerPanelLatch/New/New/New/New/Geom3D_/M06_Steel_Smoke_17
/World/HVAC_Condenser/BreakerPanelLatch_1/New/New/New/New/overRide263/M06_Steel_Smoke_17

UsdShade.MaterialBindingAPI.ComputeBoundMaterial returns no material for the two affected latch meshes.

Validation performed:

  • Reproduced through offline USD composition using the installed Kit 109.0.3 USD libraries.
  • Inspected both building-equipment and site-equipment HVAC geometry copies; neither contains the missing latch definitions.
  • An isolated candidate using the installed site-equipment materials library resolves the missing shared Aluminum_Cast, Paint_Grey and Paint_Satin targets and eliminates the sublayer error, but does not resolve the two latch bindings. That candidate is not deployed and has not been visually approved.
  • Original asset files remain unchanged. The main DSX scene renders and camera controls work after a separate camera-framing correction; this request concerns asset dependencies.

Reproduction steps:

  1. Extract the DSX dataset 2.1 archive and open the affected HVAC asset with USD composition enabled.
  2. Check the resolved location of its ../../Materials/materials_base.usd sublayer.
  3. Inspect the two latch material binding targets listed above and compute their bound materials.

Requested deliverables:

  • The intended materials_base.usd layer at the documented HVAC location.
  • M06_Steel_Smoke_17 and every referenced shader/texture dependency, or a corrected original HVAC package containing them.
  • Package version, download location, checksums and any required compatible DSX/Kit version.
  • Confirmation whether this is a known packaging issue.

Package provenance from the saved acquisition record:

  • Source: NVIDIA NGC, nvidia/omniverse/dsx_dataset version 2.1.
  • Archive: DSX_BP_.zip, 35,099,609,304 bytes.
  • Recorded SHA-256: 14b17197fd07511a7cb3b1c054d32a003e809503794cab78c7d1b779287e0038.
  • Acquired September 5, 2026. The acquisition record reports matching archive SHA-256 and checked extraction CRCs; the full archive was not rehashed during this follow-up.
  • Blueprint checkout originally based on d940314d0593bbba1bae51e40ae7f9fd48358e18.
  • Official catalog checked September 6, 2026 still lists 2.1 as latest.

Catalog: Omniverse DSX Blueprint for AI Factories | NVIDIA NGC

No proprietary asset files or raw session logs are attached to this post.

Let me check the asset and get back to you. It should not affect the overall experience or use of the asset.

Hi there,
I downloaded the zip file and actually, it opened fine except for the following error.
2026-09-09T15:17:37Z [397,374ms] [Error] [omni.rtx] Can’t access matching files for UDIM file:/C:/Work/3D/Scenes/0%20Demos/DSX%20Blueprint/Library/Assets/Bldg_Exterior/RoofUdim/Textures/T_RoofUdim_A1_ORM.%3CUDIM%3E.png
2026-09-09T15:17:37Z [397,375ms] [Error] [omni.rtx] Can’t access matching files for UDIM file:/C:/Work/3D/Scenes/0%20Demos/DSX%20Blueprint/Library/Assets/Bldg_Exterior/RoofUdim/Textures/T_RoofUdim_A1_Normal.%3CUDIM%3E.png

Your issue is more likely due to the fact that you only have 16GB VRAM on your laptop. This DSX Blueprint is VERY heavy. It requires a massive GPU.

Here below is a shot of the complete scene and as I said, it does not in any way detract from the overall experience. What you may want to try, is just to find out exactly what the sub usd file is responsible for the error message, and open that directly. That way you can see if you still get the error message.