Vectorworks to Omniverse Workflow – How to Publish USD Without Nucleus?

Omniverse Core Platform
1

Hi ,

We’re using Vectorworks with USD Composer. I understand from the forum that we shouldn’t be using the free Nucleus version. Only one person works on a project at any one time, so I understand we wouldn’t need to upgrade to Enterprise. Also with Launcher being depreciated, we moved our USD files to a local folder on our PC and setup USD Composer to run from Kit-app-template.

However, we’ve run into a significant problem:

🛑 I understand the Vectorworks Omniverse Connector only allows us to “publish” updates to an Omniverse Nucleus Server, and there’s no option to publish to a local folder. If this isn’t correct would someone be able to help me with that?

The Issue We’re Facing:

  • we have tried to find a workaround based on the above assumptions but every time we export a new usd, with the same file name, materials on our ‘modification’ layer over the Vectorworks USD get randomly changed and some of the elements within the model get moved around.

What We Need:

🔹 A way to “publish” USD updates directly to a local folder instead of Nucleus
🔹 A Vectorworks Omniverse Connector setting that allows local publishing
🔹 Any suggestions on how to automate replacing/updating local USD files without losing referenced materials and modifications in USD Composer.

We’d love to hear from others who might have solved this issue or have a workaround.

We’re currently crippled by this issue! 😞

Any help would be greatly appreciated! 🚀

Thanks,

2

Thanks for the post. Let me try to get you some great answers quickly.

Just to clarify about Nucleus Workstation. Which is the “free” version. It is not that it is bad. But my warnings are for people that ONLY save all of their precious data in a Nucleus database file. You would want to back that up regularly and have a copy of everything that also sits OUTSIDE Nucleus as well. Just in case.

In the case of you using the Vectorworks connector and Nucleus, that is still fine and still correct. Eventually there may be a better way. I would keep using Nucleus workstation and the connector, but just back up those files.

3

Thank you. We have moved back onto the Nucleus and are creating a backup

1 Like
4

Ok great