Create-2021.1: Extremely unstable and buggy, keeps hanging

I’ve spent a couple of hours trying to get Create-2021.1 up and running. Most of the USD examples don’t even run. e.g. I tried loading the Marbles example and it didn’t complete loading the file after 1 hour of waiting to load the example USD file.

I have an i7 4.5GHz system with 32GB DDR4 RAM, 2TB NVMe drive and and NVIDIA RTX Quadro 5000. Yet the software can’t even load and run and example.

The only scene that I was able to get running was a default example by manually launching a script in the install directory: ~/.local/share/ov/pkg/create-2021.1.0/omni.create.testing.sh

Has any one else experienced similar issues?

Hey elvis3, I’m sorry it’s not running for you yet. We are looking into it and will let you know if we need additional info…stay tuned!

Cheers,
Edmar

Omniverse Resources:
Open Beta | Documentation | Videos | Roadmap | Twitter | Discord (coming soon!)

Hi @edowson, just wanted to ask for a bit more information.

It sounds like you’re running on Linux: can you share your distro (and version), as well as GPU driver version? nvidia-smi will provide you the driver version in a terminal.

Do you have any other GPUs in your system?

This definitely doesn’t sound correct. One thing to note is that the samples are pulled from the internet, which could have a dramatic impact on load times if your internet connection is slow (but the samples are not that big, one hour doesn’t seem right).

I am running Ubuntu-20.04.2.

cat /etc/lst-release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"

This is the output of the nvidia-smi command:

Fri Apr 16 10:19:00 2021       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.39       Driver Version: 460.39       CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Quadro RTX 5000     Off  | 00000000:01:00.0  On |                  Off |
| 33%   33C    P8     7W / 230W |    339MiB / 16122MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1205      G   /usr/lib/xorg/Xorg                 77MiB |
|    0   N/A  N/A      1926      G   /usr/lib/xorg/Xorg                110MiB |
|    0   N/A  N/A      2058      G   /usr/bin/gnome-shell              141MiB |
+-----------------------------------------------------------------------------+

The nvidia driver that is currently installed is the ` package from the Ubuntu repository:

ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001EB0sv000010DEsd0000129Fbc03sc00i00
vendor   : NVIDIA Corporation
model    : TU104GL [Quadro RTX 5000]
driver   : nvidia-driver-460 - distro non-free recommended
driver   : nvidia-driver-450 - distro non-free
driver   : nvidia-driver-418-server - distro non-free
driver   : nvidia-driver-460-server - distro non-free
driver   : nvidia-driver-450-server - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

As far as the samples are concerned, I installed the nucleus server, manually downloaded the samples, e.g. Marbles example which is 4.7GB compressed, extracted the files and then attempted to load the Marbles.usd file using create-2021.1.0.

I installed the nvidia proprietary driver after uninstalling the ubuntu nvidia-driver-460 package and create-2021.1.0 launched correct.

Fri Apr 16 11:01:00 2021       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.73.01    Driver Version: 460.73.01    CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Quadro RTX 5000     Off  | 00000000:01:00.0  On |                  Off |
| 33%   42C    P8     8W / 230W |    304MiB / 16122MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1107      G   /usr/lib/xorg/Xorg                 77MiB |
|    0   N/A  N/A      1849      G   /usr/lib/xorg/Xorg                 90MiB |
|    0   N/A  N/A      1980      G   /usr/bin/gnome-shell              126MiB |
+-----------------------------------------------------------------------------+

However, the Marbles example just shows a dark stage with a couple of cameras. Nothing gets rendered.

Right on, thanks for all the details!

I believe both of those drivers should have been OK.

Question: what happens when you try to open omniverse://localhost/NVIDIA/Samples/Marbles/Marbles_Assets.usd? I’m specifically interested in the version that comes from the localhost Nucleus Server, on that exact path.

The way these things are implemented is that we host our Samples in AWS S3, and the Nucleus installation comes preconfigured so that your localhost exposes these files transparently.

Is the path above where you tried to download Marbles in the first place? If so, how did you download it? Downloading USD Stages is a bit special, one .usd file can end up referencing many other .usd files and really any other file in the filesystem.

I’d be interested in seeing the Layers panel as well with your broken output.

In any case, I can try to repro this on Monday, but I’d like to hear how it goes if you try loading the scene straight from the path above.

Have a great weekend!
Matt

I have uninstalled Create and Nucleus from my system.

To answer your question:
A01: I downloaded and extracted the Marbles samples to a path on my home folder. I attempted to open the usd file from create-2021.1.0’s File → Open menu option.

Ah, sorry to hear that. I tried opening the Sample directly from the /NVIDIA/Samples/... path on Ubuntu 20.04, and I was able to open it in an edit layer, or just by itself without issues. That said, the internet connection is quite fast. Marbles itself weighs in at about 4.3GB, so if your internet connection is not that fast, you will definitely feel that during opening the stage.

For future reference (and anyone else who ends up with the same problem), I was able to reproduce your problem, and it is as I feared.

If you right click a file in Content Browser and select Download you will not get the full USD Stage and all its dependencies downloaded. You will download only that exact file, and in this case, it is the layer that composes the entire Marble Assets scene.

This is the button I’m talking about:
image

And this is what happens when I download it to my disk, and open it (on Windows even, but this is platform agnostic):

Now, if you go to the Layers tab, and expand some of the trees, you’ll see that all the references are actually missing (red text, and the tooltip on mouseover):

The Fix: In order to acquire the entire USD Stage composed in a Layer, and all its dependencies (other USD Layers, Textures, etc), you must click Collect Asset instead:
image

I think that the user discovery here is opaque to say the best and I’ll raise the issue on the internal ticket.

Even then, there is one more important thing to know, when you click Collect Asset you’ll get the next popup:
image

And here it is important to set the Collection Path somewhere on your local disk.

Two final remarks: First, while our Samples are accessed via Nucleus+S3 and can take a long time to download the first time you open them, they will be cached by default (as long as your Cache signal is green in Create in the upper right corner) on your local disk, transparent to you.

So every time you open that path in the future, even though it looks like its coming from a Nucleus server, they will actually open locally from your disk and skip the entire download stage.

Second, you may have this question:

So how would I make changes to the stage though? I can’t actually save stages to the /NVIDIA path?

This is where the strength and elegance of USD comes into play: You can create a new empty USD Layer on your disk (File → New), and simply reference in the Marbles sample by dragging it in from the Content Browser to the viewport (note if its the first time with Marbles, it’ll be slow as it downloads everything and compiles the materials).

After that, any change you make to the scene will be stored in your local layer file as an override to the Marbles sample, and you are free to modify and safe it as you wish. Here’s an example after a few transform edits, you can see the changed Xforms appearing in the Layer tab:

Hopefully this helps in the future. Sorry for all hassles you had, and we’ll work to make the user experience smoother in the future.

Matt