Omniverse USD Composer (enterprise) long starting

Everytime I am starting USD composer I need to wait up to 30-40 minutes.
It stucked on 7,10,12% of app loading.

In log I see the app is waiting for timeout. But I expected a true on demand run for Enterprise version.

2024-03-18 08:42:20 [80,357ms] [Info] [omni.client.plugin] HTTP Client: http: libcurl error (28): Timeout was reached for https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml
2024-03-18 08:43:21 [140,457ms] [Info] [omni.client.plugin] HTTP Client: http: libcurl error (28): Timeout was reached for https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml
2024-03-18 08:44:22 [201,558ms] [Info] [omni.client.plugin] HTTP Client: http: libcurl error (28): Timeout was reached for https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml
2024-03-18 08:45:23 [262,658ms] [Info] [omni.client.plugin] HTTP Client: http: libcurl error (28): Timeout was reached for https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml
2024-03-18 08:46:24 [323,760ms] [Info] [omni.client.plugin] HTTP Client: http: libcurl error (28): Timeout was reached for https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml

Yes I can see that. It seems like you are having a connection issue to our required online resources. It is slow because it is waiting to connect until it times out to each resource, and there are hundreds. So first check your internet connection. Second check your firewall settings. Are you in a corporate setting or in a country that is forbidden from access ? The best thing to try first is to take one of those http addresses gnat is failing in your log and simply copy and paste the address into your browser and see if you can get there and download it. If not, that’s the problem.

Can you get to https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml

Hi Richard, Yes I can reach the *.toml file via link from browser. But Omniverse USD Composer can´t.

  1. Are you running the latest version 2023.2.5 ?
  2. If so can you reset it by going into “Preferences” and then “Resetting” it.
    image

Yes I am running the latest 2023.2.5. I tried the reset but same behavior.

So you are still able to run USD Composer 2023.2.5 but it starts very slowly ? This is certainly a firewall or local realtime anti-virus software. I just had this happen with a client running Digital Gaurdian. You can try to reinstall or reset, but it really sounds like your security environment.

When you start up next time, go to Task Manager and look at your DETAILS tab. View by CPU and you should see WHY it is taking so long. When I did this on that system I saw that only 2% was loading composer. 98% was the anti virus.

I thing it is something about proxy. Directly from browser I can reach https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml. But compose cannot. But I think developers should make a timer shorter, or disable this feature because of enterprise/onpremise solution.

So are you confirming then, that you can start and run USD Composer but it takes a long time to start ? Please attach fresh logs so we can see and if you can record a video of it starting slowly.

Once the program starts, does it run normally ?

Why don’t you temporarily disable all security software on your computer. Disable your firewall and disable your anti-virus and see.

Is this a personal machine or part of a corporate network ? If it is part of a corporate network, just contact your IT admin and talk to him about what is blocking it.

You must be able to talk to these three places:

Kit Kernel and Content: d4i3qtqj3r0z5.cloudfront.net
Extension Registry: ovextensionsprod.blob.core.windows.net
s3 Prod: https://omniverse-content-production.s3.us-west-2.amazonaws.com

Yes. this is what I am typing on beginning. It takes up to 40minutes to start, because app is waiting for internal timers.
2024-03-18 08:42:20 [80,357ms] [Info] [omni.client.plugin] HTTP Client: http: libcurl error (28): Timeout was reached for https://omniverse-content-production.s3.us-west-2.amazonaws.com/.cloudfront.toml

And I am asking how to “bypass” this behavior. I can´t turn of security etc. It is a corporate PC, enviroment, very strict conditions. My question is why the Omniverse enterprise does not have features how to run composer in a strict enviroment.

Ah I see. So then you know the answer. Talk to your IT dept about allowing the program to run. We work with very large corp networks. But as always, you always check with your IT dept. we cannot control your restricted internet access.

Mine problem si solved by set up two global variables:
image

Yes good. That is allowing access to your local host IP and allowing port 9001 through.

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