Vectorworks to Omniverse Composer publishing - randomizes materials already applied

We publish Vectorworks models to Omniverse using the Omniverse Connector, where we apply materials and assets.

Problem 1:

  • Republishing a revised Vectorworks model into Omniverse causes materials to randomly swap and/or the model to explode with scattered objects.

The exploding is resolved by restarting omniverse but the materials are still messed up.

Things we’ve tried:

  • Objects must have a texture in Vectorworks first for Omniverse to recognize them for material application.
  • We’ve ensured consistent file names (Vectorworks and USD) to maintain paths
  • Some Vectorworks materials (e.g., ‘Almond Paint’) seem to trigger material swaps in Omniverse, while others (e.g., ‘Preview Brick 18’) do not

Problem 2:

  • Some object faces seems to be inside out, so when we use the paint tool, the painted assets appear on the opposite side of the surface. Those problem surfaces don’t seem to have a ‘normal’. The paint tool seems really buggy. We’re on v105.10.2)

Problem 3:

  • Some Curves appear facetted in Omniverse despite high 3D Conversion Resolution & Render Style Detail settings.

Any insights or solutions would be greatly appreciated! We feel like we’re the only people in the word using Omniverse with Vectorworks! 😩

Has anyone had the issue where a model’s textures get swapped when using connectors from other software. We are also asking Vectorworks to help us on this. Any response or help would be much appreciated. 🙂

I would say to both of you, could you zip up your full vectorworks projects and send them over to me in a private DM, using whatever cloud file tool you like and then I can pass them over to our dev team that is working specifically on the connectors.

1 Like