Hii there,
we have parametric modelling in CAD. for now lets say using CATIA we an bind them with relations.
How can we do the exact using usd. I am trying to alter the usd file by building a python UI extension integrated with USD composer of NVIDIA Omniverse.
Hi Mohit,
This comes up a lot when teams move from CAD into USD. My recommendation would be to keep parametric modeling in CATIA rather than trying to recreate it inside USD.
USD is a scene description and composition format — it represents resolved state, not the modeling logic that produced it. Building parametric dependencies on top of USD (via Python listeners, OmniGraph, etc.) would mean writing a custom constraint solver that’s fragile, hard to maintain, and can’t round-trip back to CATIA.
The better investment is in your CATIA-to-USD export pipeline — automate the re-publish from CATIA to USD when parameters change, rather than trying to make USD itself parametric. Take a look at GitHub - NVIDIA-Omniverse/usd-exchange: OpenUSD Exchange SDK · GitHub — it won’t solve every part of the problem (you’ll still need to handle tessellation and structure mapping on the CATIA side), but it’s the right place to start for authoring correct USD output. If you run into gaps, file Issues there — the team triages them.