Failed to create GPU for compatibility mode

[romichel2003]

Hi Everyone,

I use to have one RTX A4000, and it was working fine. I added a second RTX A4000, updated the driver to the latest, and now I can’t open any application from the Omniverse Launcher anymore. I get an error message “Failed to create any GPU devices for compatibility mode”.

However, according to the NVIDIA control panel, both my GPUs are up and running.

I am on Windows 11.

Any idea on what is happening?

[Simplychenable]

@romichel2003 i am just another OV user, would it be possible for you to upload the launcher.log for eval? perhaps there are additional information that could facilitate troubleshooting process.

%userprofile%\.nvidia-omniverse\logs\launcher.log

[romichel2003]

Hi @Simplychenable
Here is the launcher. Yesterday was the first time I tried to open an Omniverse application, so only the data from 2024-01-31 13:22:05.077 to 2024-01-31 22:00.
I am using the latest one (R550).
launcher.log (846.4 KB)

[Simplychenable]

is this on a personal machine or part of a enterprise equipment? can you try a few things? one thing i am trying to determine is whether you have file/folder access permission issue. if it’s an office equipment, check with your IT to make sure configurations are all proper. could you also confirm again if the apps you have installed are all having the same problem (Blender, Code, Create XR, and Composer) or just Composer?

• relogging - log out of the OV launcher and log back in. better yet, reboot your machine if you haven’t since the Launcher installation.
• deleting kit files - close out of all OV related apps including the Launcher, then navigate to C:\Users\Rosaire\AppData\Local\ov\data\Kit and delete all the subfolders and their contents from that directory.
• GPU driver clean install - try reinstalling the display driver again but this time do a clean install. you should see that option in the installer.
• update the .bat file to force multi gpu - open to C:\Users\Rosaire\AppData\Local\ov\pkg\create-2023.2.2\omni.create.bat and edit the file to look like the snippet below:

@echo off
setlocal
call “%~dp0kit\kit.exe” “%%~dp0apps/omni.create.kit” %* –/renderer/multiGpu/enabled=true

i see some errors regarding network disruption but i am unsure if it’s related to the GPU issue. let’s try the two options first and see what happens. also, what’s R550?

[romichel2003]

Thanks for your inputs.
I am using a personal machine. The problem is with all OV apps, except Blender 4.0
I tried the all the points you listed with no success. Here are the logs
log_forcing_multigpu.txt (8.6 KB)
crash_2024-02-02_08-57-14_15468.txt (6.1 KB)

There is seems to be an issue with a plugin (carb.graphics-direct3d.plugin), but i have no idea if it is the cause or the consequence of the issue I am facing.

[Simplychenable]

there’s another line from the log that stood out for me:

[carb.graphics-direct3d.plugin] Aftermath D3D12 failed to initialize.

and in the crash log, it reports:

[crash]  aftermath_version = '2022.2'

i will defer to the mods/devs on this because they will certainly know more about the technical aspect rather than me speculating.

[SohailMehdi]

i am facing same problem with usd composer and Omniverse Machinima work fine

mine .i am using [

NVIDIA GeForce RTX 2060 is my graphics card is not compitable or there is some problem with omniverse usd composer ?

[pandorazero]

I faced the same problem but I have an rtx 3060ti video card
Can you help solve the problem?

crash_2024-02-24_15-30-44_836.txt (7.1 KB)

[cwbruner]

Same problem on linux. I’m using cuda and RTX 4090. Running nvidia-smi shows 483MiB/24564Mib which should be well over what is needed.
This is my initial experience with this software and so far… I’ve had more fun building a gentoo distro.

[sean.xc.guan]

Same Problem on my laptop Unbuntu 22.04~
I’m using RTX 4080.
Isaac sim version: 23.1.1
RTX Driver: 525.147.05;
Cuda : 12.0 (BTW, I’ve ran cuda samples successfully.)
Could any one help~

[Simplychenable]

@sean.xc.guan have you tried doing a clean install of the same driver or getting a slightly newer driver to see if anything changes on your end? if inclined, could you also upload the OV Launcher log and the nvidia-smi report ?

[remark3dcz]

Same problem RTX 3060 12GB - last studio nvidia driver

launcher.log (315.6 KB)

[Richard3D]

Could you try downgrading your driver to the last official compatible driver please. 537.58
Technical Requirements — Omniverse USD Composer latest documentation (nvidia.com)

[Richard3D]

Here is a post with the same issue that was solved by backing down the driver to 537.58
Audio2Face Not Launching After Changing GPU - Apps / Audio2Face - NVIDIA Developer Forums

[remark3dcz]

@Richard3D

537.58

Hello,
thank you for your response to the problem.
First of all I have to clarify that I used Omniverse with USD Composer and other omnivers apps without any problems on the same PC setup that I use now. The problem arose when I was forced to reinstall W11 and it seems that with the new version of W11, or rather its latest update, the same problem arose already in February this year. After reading about similar problems with other users, I assumed that I simply had to wait for a fix from you. At that time I tried downgrading various older versions of USD composer, but nothing helped, so I uninstalled everything and tried again after half a year, new versions of both nvidia drivers and your Omniverse came out. But nothing changed, still the same problem. Even during installation a message pops up about not finding a compatible GPU. And the Composer application itself can’t be launched after the installation is complete.

I couldn’t get USD Composer to work at all, I used Drive to import and render USD from IC8 or CC4 (from Reallusion).

Anyway I tried to downgrade nvidia driver to version 537.58 as you recommend. See installation screenshots and I reinstalled Omniverse launcher and started installing USD Composer application.

Now the installation was done without the GPU error. And USD Composer started after installation and launch! :-) see screenshot. Thank you very much for this advice, it helped, however I consider it a temporary solution, due to work in many programs using GPU I would like to work with the latest nvidia drivers.

Now it is obvious where the problem might be. Could you please let me know if you manage to find the problem and fix the fix for the latest nvidia drivers as well?

If you need any further information, let me know.

Unfortunately, I have completely deleted the previous installations and I don’t have the USD Composer log anymore. I would have to delete everything and install the latest nvidia drivers to repeat the error.

Kind regards
Martin

[Richard3D]

Great !! That is great to hear. I understand that not always running the very latest drivers can be fustrating. It does vary a lot from person to person, computer to computer. For example I am running the latest drivers and I am fine. It is not always an exact science, but a suggestion.

Feel free to upgrade drivers in the future and see how they respond. At least we have you back to work.