Hi,
I just downloaded the latest release of USD Composer and it is crashing when I try to launch it, 2023.2.1 still launches fine.
I should also note that USD Explorer crashes with the same error.
kit_20231220_102058.log (525.5 KB)
launcher.log (1.6 MB)
omni.kit.internal.log (931.6 KB)
omni.kit.sysinfo.log (80.0 KB)
@Drew.CERN i wonder if it’ll help using a newer version of the driver, like the 535s. this is comes from mainly seeing the error in the log:
2023-12-20 09:21:01 [3,016ms] [Error] [carb.graphics-vulkan.plugin] VkResult: ERROR_INITIALIZATION_FAILED
2023-12-20 09:21:01 [3,016ms] [Error] [carb.graphics-vulkan.plugin] vkCreateSwapchainKHR failed.
2023-12-20 09:21:01 [3,016ms] [Error] [carb.graphics-vulkan.plugin] Failed to create a swapchain.
2023-12-20 09:21:01 [3,016ms] [Error] [omni.kit.renderer.plugin] createSwapchain failed. Width: 65516, height: 1022, Format: 9
2023-12-20 09:21:01 [3,017ms] [Error] [omni.kit.renderer.plugin] Failed to initialize graphics environment.
and, i know this isn’t for the Composer app, but there’s a section from the Isaac Sim doc that could offer additional insight for troubleshooting Linux issues and may be worth taking a quick glance over - Linux Troubleshooting — Omniverse Developer Guide latest documentation
Thanks, I’ll take a look. I was trying with 545 before and had the same error, the documentation I read suggested using the latest 525 version. I’ll try with 535 and see if it helps.
I’ve tested it with 535 and unfortunately I get the same error. Which log did you find the error in? I saw an imgui error in kit_20231220_102058.log which I’m guessing is being caused by this Vulkan error.
It’s strange that the error is only happening in the latest version of USD Explorer and USD Composer, but not in 2023.2.1 of Composer.
i saw the error in the kit log. can you elaborate on when it crashes? does it occur before or after the Composer window outline is shown?
also, i am curious when you installed the update? as another user, i generally try to wait until an official announcement on the forum before attempting the install. i find getting the update off hot off the press could sometimes lead to install bug. although i cannot confirm nor deny this is the case, but one thing you could try doing is reinstall it to see if anything changes.
Hi, it crashes before the composer window shows up. I installed the update this morning (Europe Time) as the launcher prompted me to. I’ll try a reinstall tomorrow and see if it fixes it.
i will review the logs again to see if there’s anything else worth mentioning while we wait for the mods/devs to chime in.
For what it’s worth, I also see this in your .LOG file:
[Warning] [gpu.foundation.plugin] IOMMU is enabled. Found 15 items in /sys/kernel/iommu_groups/.
[Warning] [gpu.foundation.plugin] An input-output memory management unit (IOMMU) appears to be enabled on this system. On bare-metal Linux systems, CUDA and the display driver do not support IOMMU-enabled PCIe peer to peer memory copy. If you are on a bare-metal Linux system, please disable the IOMMU. Otherwise you risk image corruption and program instability. This typically can be controlled via BIOS settings (Intel Virtualization Technology for Directed I/O (VT-d) or AMD I/O Virtualization Technology (AMD-Vi)) and kernel parameters (iommu, intel_iommu, amd_iommu). Note that in virtual machines with GPU pass-through (vGPU) the IOMMU needs to be enabled. Since we can not reliably detect whether this system is bare-metal or a virtual machine, we show this warning in any case when an IOMMU appears to be enabled.