Tring to update kit to 106.5 via launcher, but getting this error:
Error occurred during installation of Kit: [94e7976d-1451-4798-9135-ae3660cf5aae] Cannot prepare file for download, the server has returned HTTP403 for signed URL https://asset.launcher.omniverse.nvidia.com/orgs/nvidia/teams/omniverse/resources/kit-sdk-windows[...]
Hey @brainstencil
Sorry you’re dealing with this, but looks like you are being blocked from a VPN or location. Are you on a VPN?
~ Ashley
Hello!
I am having the same issue (for a few days, actually). I’ve tried on three computers (work and personal account), with and without VPN and the same error occurs.
I too have this issue. No VPN, other apps update properly, tried on two machines.
Thanks for the feedback, everyone! Let me connect with the KIT KAT team and return with more information soon
Ah, perhaps the issue is launcher. We suggest that Kit 106 templates, including the latest Kit 106.5, is installed via github at NVIDIA-Omniverse/kit-app-template: Omniverse Kit App Template
It’s super easy to create your kit app with this repository, but please let me know if you need any help as you move over to the kit-app-template workflow from launcher
Is the standard composer one of the templates or do we need to figure out what extensions to load?
I followed the “Quick Start” instructions, and the third thing you need to pick is the template. The name of it indicates that USD composer is one of the templates:
@brainstencil the USD Composer template is essentially a clone of the one from Launcher with the same extensions
Thanks! I will build this
We do not use Launcher for kit downloads anymore. Please start to transition away from Launcher. The kit sdk page just takes you to our new NGC location. We are transitioning away into two distinct places and branches. From now on Launcher will just point to our NGC Catalogue for the “Production Branch” of Kit, currently 106.5. For the “feature branch” moving from here, on our, we will have our GitHub Page update regularly with our “Kat”, Kit App Template. Currently both versions align. But as we update to kit 106.6, ONLY GITHUB will update, until the next Production Branch later this year. I would stick with GitHub for the latest and greatest. Production Branch is intended for Enterprise, that require non beta code.
PRODUCTION BRANCH >> [Kit SDK | NVIDIA NGC (Kit SDK | NVIDIA NGC) (Requires Signup)
FEATURE BRANCH >> GitHub - NVIDIA-Omniverse/kit-app-template: Omniverse Kit App Template
I built the template based on composer from the kit-app-template repo and it does not have feature parity with the composer found in launcher. Tons of things missing, for example the extensions window isn’t available. I noticed Performance was abysmal compared to 120fp in launcher composer in the exact same scene.
It seems to me that it’s not just launcher being deprecated. Is there a fast way to revise the template so that custom built app matches?
I assume you are comparing the old Kit 105.2 and USD Composer 2023.2.5, to the new Kit 106.5 template? The performance should be several X times faster. What GPU are you using? You may not be comparing apples to apples here. Make sure you are comparing the exact same viewport resolution settings. We have raised the default resolution since then. You would have to go into both composers and set them both to “Fill Viewport” OFF and then set a fixed resolution of say, 1080p. Then both on realtime. You should see a massive improvement depending on your hardware.
For the extensions window, this is easily turned on by adding the “-d” to the launch code. So now make it “repo launch -d” and you will see all of those developer settings come back. Extension Manager, console, debug etc.
Hi,
The GPU is a 4090.
I’m comparing USD Composer (Via Launcher on Kit 106.4) vs Composer via Kit-App-Template (new clone of repo, assuming 106.5).
I normalized the viewport settings to 1280x720 and fill viewport off:
Template Composer:12 fps
Launcher Composer 160 fps
I was able to load the extensions by launching with -d, but there are still so many things missing. I assume I just need to add them in, but the problem is knowing what to add in.
And what happens when I load a USD file that uses functionality that came with one composer but isn’t available in another? By any chance could it obliterate performance?
12fps vs 160fps ? Something is not right there. I think I know. We have massively increased the ECO MODE timeout number. From 100 to 500. That means it used to render just 100 passes in realtime before finishing and you will see your frame rate go from working mode to resting mode, and go way way up. In the new version, now being 500, that will take 5 x as long to get there. So you might be comparing the old version “at rest” after its finished just 100 passes, and the new version “rendering”.
To do another comparison, set both to 50. Then look at the “rendering” frames per second and then the “resting” frames per second. You should see the fps shoot way up on both.
I did some more testing with this and set the Eco mode to 50.
I tried to do a side by side with exact settings and see the difference (I realize that’s probably not the best way to measure performance) and with a simple scene the new Kit version was much faster. In the full scene, where I have a lot more complexity, the kit version still seems to be slower.
But I have action graphs and motion matching and behavior scripts (all built in the launcher version of composer), so I’m wondering if the difference in performance is related to the fact that the stage is using extensions that are not loaded?
I’m not sure but it’s not a show stopper for me right now, and I’m not able to share the scene externally so I’m not going to try to solve it at this point.
Regarding the features in composer from launcher vs kit app, I made a new post about that so we don’t have to discuss across different subjects:
thanks for your help.
Well I am trying to help you, truly. So I appreciate that. But it your video you had two templates running side by side. The old and the new. You really should evaluate them one at a time. I know its more work, but kit runs best when it gets 100% of the resources. Sharing the cpu and gpu is not great.
I understand that it’s not a great way to measure performance to have both open at the same time. But
making a comparison between 2 applications that have completely different default settings, and even worse, a different SET of settings, it’s really hard to setup a test that compares apples to apples. As I mentioned in the other thread, the apps just aren’t even close to the same environment.
Take for example that the render settings in the kit app template version of composer contains about half of the settings that the launcher composer has. Even when I load the same project some of these settings are overridden… Like the eco mode setting you told me to change, and the viewport settings… I do not have a clue how to be sure that each instance is configured the same way. I’m also testing across 2 different workstations (3090 and 4090).
In a simple scene that I build with one asset, the kit app template version seems to be way more performant (on the 3090). But the scene that I’m working on is so much more complex. The frame-rate is way more variable on the 106.5 version, but the lows are lower than the launcher version.
My thinking is that I will abandon the kit app template and we will redo all of the materials in a way that’s compatible with 106.4 and I’ll roll back to using the launcher.
Well obviously you do whatever is best for you. But I would strongly advise you move forward with latest version. We are about to release the next. Ideally you do not want to go backwards. And Launcher itself is now Legacy. I am sure, 1000% sure that kit 106.5 is the best for your needs, and much much faster.
