STEP→USD conversion yields tn_ prefix and random ID suffix on prim names

Operating System:
Windows
Kit Version:
107 (Kit App Template)
Kit Template:
USD Composer

Hello everyone,

I’m using the Omniverse HOOPS Converter extension (omni.kit.converter.hoops) version 507.503 to convert STEP (.stp) files into USD, but I keep running into a naming fallback issue. Although every part in my STEP file has a proper name, the resulting USD prims are named like:

tn__M25_4_523L_WF
tn__SCREW_FLAT_440_5_XO

—that is, they’re automatically prefixed with tn_ (“Tessellation Node”) and suffixed with what looks like a random hash, instead of preserving the original entity names
Note: This does not happen on every part—some prims correctly keep their CAD names, but many fall back to the tn_… scheme.

Ok thanks for letting us know. It may be a minor bug with the converter. I will let the engineering team know. There may be a pattern to it.

From Engineering:

Hi Richard, the user is seeing their model element’s names trancoded into valid USD prim names.

USD (Universal Scene Description) has some naming rules. To follow these rules, we “transcode” any names that don’t fit by converting invalid characters into valid ones.
If you want to view your original names (before they were changed), you can do that in the Omniverse app by:

  1. Locate the “Stage” tab (right-hand side of window).
  2. Left-click on the “hamburger” menu.
  3. Select Show Display Names.

This will show the original names you’re used to seeing, instead of the transcoded ones.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.