In our ongoing effort to improve the Omniverse platform for developers, Omniverse Launcher will officially be deprecated. Launcher will remain available without support until October 1, 2025.
Omniverse resources will be relocated to platforms where they are better accessible for developers:
Omniverse samples and templates can be found on GitHub and the NGC Catalog.
Will Nvidia be migrating to a new platform for accessing these omniverse tools? I use the launcher for running Isaac Sim. Is Isaac Sim being depreciated as well or can this be accessed without the launcher?
Isaac Sim is not being depreciated, no. It will still be available on Launcher until October, but starting soon, Isaac Sim will be also available as a direct download as well, without needing Launcher.
How about the end users who use USD Composer? It is not clear if this upcoming change about the launcher or whether this change affects all the underlying applications.
Omniverse Launcher is a very useful and integral part of the development experience.
We had a single place (single source of truth) where we could access all installed applications. All third-party packages/services were discoverable too. Most importantly, each app had its own documentation and tutorial section, which was handy for getting started or for quick reference.
In my opinion, discontinuing the Launcher is a strategically bad move unless there is a strong logical explanation that defeats the purpose of usability and having a single place for information.
Actually, Launcher is not required at all for Omniverse and Kit. It is just a simple UI for launching our code. We do not have applications, we have TEMPLATES. The connectors are also required less and less because so many applications are going full USD support.
So really all we have is the kit core code, some extensions and our Kit App Templates which are now on GitHub
With the launcher going depreciated together with nucleus workstation . I have a question on the new setup in term of file sharing/references for using USDcomposer because from my understanding file sharing and network access capabilities are gone with no nucleus workstation.
Currently I have a very basic computer server (Local LAN) that is just running nucleus workstation with all my library files/project files stored and I access/references these using my main computer by connecting using nucleus via IP address.
So with nucleus workstation gone, is there a way to access/reference library resources stored on my computer server(Local LAN) or just via a network drive ?
OK and thanks for your question. My reply may surprise you, but you are in grave danger of losing all of your work if you’re only using nucleus free on a workstation version. Unlike nucleus enterprise, there are no daily backups. If your nucleus, drive or data cache, becomes corrupted in anyway you will lose everything. All of your work.
Nucleus for workstation was just recommended as a trial sample for gaining greater access to nucleus enterprise. It is highly recommended not to use it for actual work.
What I would do straight away is get all of your files, at least copied out of nucleus into regular windows explorer. I personally never use nucleus. Simply open everything you have a nucleus and save the project to a normal Windows computer drive. Then you can access these files normally, and on several other machines over a local network. This is far safer.
I would actually go a lot further and get these files backed up with something like OneDrive or dropbox. I actually use dropbox with my Omniverse, not nucleus.
From what you’re saying, I gathered that even without nucleus it is possible to just browse to a network address (LAN machine or cloud drives like Onedrive, dropbox, google drive etc.) from USDcomposer.
Is there an example/guide on how to do that, cause I can’t point to any network address in USDcomposer that is not nucleus and have not found a way to browse to any other location other than the local drives on my computer.
Well you get around that by mapping network drives. With my Dropbox, I just have D:/Dropbox. So to access that I just go there as normal. That will the same with any “cloud-to-disk” program. For one drive you again just go to your one drive folder as normal.
You are right. Content Browser is for “local” content but that is fine for those kinds of programs. For a network drive on another machine you can “map” that drive. For a guide on that just google “mapping a network drive”.
“From the toolbar, select “Map Network Drive.” Click on it to open the mapping window. You will be prompted to select a drive and folder.”
So for me, I went to my machine A, navigated to my machine B through the network, and then mapped my entire “Projects” folder on machine B as a new “Z Drive” on machine A. Then I can go into USD Composer on machine A and select my “Z Drive”, and then I can load projects from machine B.
This is a common way to “trick” windows and Windows app into thinking a network location is just another local drive.
I have been off the platform for several months on another project. I have come back just now and getting my head back into the platform. My first port of call was USD Presenter. It looks like it doesn’t exist any more? Has it been replaced by another App?
Also I am reading the Omniverse Launcher is been depreciated. I am not sure what that means in detail. Any videos that go into deep on this?
Welcome back. All the previous templates like USD Presenter, USD Composer, etc have been removed and condensed into one master template system called the kit app template. This template is available for free on our GitHub page at GitHub - NVIDIA-Omniverse/kit-app-template: Omniverse Kit App Template
The only legacy template still on Launcher is USD Composer. But that is last year’s version. Yes the Launcher will go end of life in October. You do not need it. Everything is going to a developers platform with just kit and kit templates.
I did a build of 106.5 kit app and turn on most of the stuffs I need like RT2.0,Iray, section tool etc. in extension manager but once I package the app and when I start it up, most of the extension I did turn on was there like RT2.0,Iray but extension manager tab is not there. How can I package and run the app that have extension manager available ? Thank you.
@DavidDPD I think the point of packaging the app is to “deliver” it to your client where they CANNOT access the Extension manager, or change the program in any way. That is the point. You would not want to deliver it to your client and they start turning things on and off, and changing settings. What ships is whatever ships. And that is up to you to include it before you package it.
Based on what you are saying , the end users should have no way to access extension manager ? This is weird and counter intuitive because most things on kit is modular and mean to work as an extension therefore it can be toggle on and off when needed , it also encourages developers to develop extensions that can be share and access by others (just like it is now in the launcher version where you can access community developed extension ).
By removing the ability of accessing extension manager for end user now, I don’t see how it helps the end user or even developers of extensions because who then knows what extension is available in the community and why are developer even interested in doing extensions then when its kind of silo and inaccessible.
I think most of us transiting from launcher version to Kit is just asking for feature parity, of course we understand not everything remains as is but we hope the functionality remains.
Who are you developing this app for? You are the developer, and you should have access to the Extension Manager, because you need to design the app to work the way your end user will need to use it. The end user, by definition will be instructed to use the app you built, the way you built it, with the features you wish to include.
Otherwise, your end user may as well just download his own kit file and make it the way he wants, and there is no need for you in the middle. We are making a developer platform, for you the developer to either make something for yourself, or for your client.
Having said this, if you want to include the Extension Manager, it is fairly easy to do. You can just include the extension manager extension into your kit file dependencies, and it should work fine.
Hi, I want to capture 2D images from an environment using replicator headless mode. The original tutorial uses the Omniverse Launcher. If I switch to using the kit-app-template, how should I perform the replicator headless workflow? Could you please provide a reference process?
