I am trying to open an assembly file with a large number of models using USD Explorer, but I keep getting a low memory message and the process stops.
I am able to open the same project using Composer or Presenter on any of the machines connected to the Nucleus. These machines vary from a 3060 Ti to a Quadro 4000. The host PC is the only one able to open the project in USD Explorer and it has a 6000 Ada card.
The only thing I can think of is that USD Explorer by default has FSD (Fabric Scene Delegate) on by default. And actually, it is hard wired to be on. Normally, FSD really helps with massive models which is why we have it on for Explorer, but it is possible it is causing issues with your file in particular.
What you can try is to start USD Composer, and before you open the file, go to Preferences > Rendering and turn ON Fabric. Then see if this causes you the same issue. This will help confirm an issue with FSD. There is a memory slider on that screen, and you can try different settings. It may be that you need it higher from 80% to 90% or more.
Try that and let me know.
Changing the FSD option didn’t work.
I copied the assembly file and the sources for the models without the materials and was able to open it in Explorer. The only difference was the missing materials from the nucleus library, so I think the bottleneck is the number of materials. I tried running the Scene optimizer in Explorer, but it didn’t help with the queue.
Also, is there a way to render images in Explorer and not just ttake screenshots? Presenter had an important role in our Archiz pipeline, so I hoped that Explorer had at least the same features after Presenter was removed from the launcher and we were told to use Explorer instead.
My advice is that you sound like a power user and use should be using our main flagship template, which will always been USD Composer. I would not attempt your advanced workflow in Explorer. Explorer was made for more basic viewing and reviewing operations by non-technical parties. USD Composer gives you the full power of anything you want to do. Explorer does not do Rendering, no, but USD Composer very much does. Get the latest version here GitHub - NVIDIA-Omniverse/kit-app-template: Omniverse Kit App Template
We indeed use Composer to create our AEC projects and render the final products. As you mentioned about Explorer, we were using Presenter as a tool our clients with less technical knowledge could use to review projects, and having a few extra rendering options was useful when checking lighting and material options.
I just think it was not the right move to deprecate Presenter and replace it with an app that struggles to open the same files and doesn’t have the same features.
I will reduce the number of models in the file until I find a way to unpause the queue in Explorer.
Are there any other settings you think could help?
Thanks
Ok but remember that kit and omniverse is a fully customizable platform and code. Just take Composer and hide what you don’t want your client to see in the kit file and send that “your” version of Composer. Change the colors, change the name, add features. Take them away. Make it YOUR composer for your clients. That is the idea.