The "Audio2Face" program crashes after launching on Windows 10

Windows 10 version 21H1, AMD Ryzen 7 with 8 cores, 32 GB RAM, graphics card nVidia RTX 2070, 2xSSD 1 TB M.2, latest GPU driver.
The program starts, hangs for a couple of minutes and then quits.

Hello @iliakutaev! Welcome to the Community. Sorry to hear you are encountering a problem. Without the logs, it sounds like you might be running out of GPU memory?
The Technical Requirements suggest using a RTX 3090 with at least 16GB of VRAM

Would you be able to attach your logs for Audio2Face? You can find them here: C:\Users<USERNAME>.nvidia-omniverse\logs\Kit\Audio2Face

Hi there!

I have a similar issue. I have been struggling with this for about 5 months now, tried different versions of A2F, but the same thing happens every time: a lot of flickering and a crash after a couple minutes (sometimes seconds).

Specs: AMD Radeon, NVIDIA GeForce RTX 3070 (laptop), RAM: 32 GB

I’m guessing it’s this part of the logs that causes an issue:

2022-05-16 13:00:20 [46,371ms] [Info] [omni.audio2face.tool.scripts.utils] [omni.audio2face.tool] Stage opened
2022-05-16 13:00:20 [46,371ms] [Info] [omni.kit.app.impl] [py stdout]: [omni.audio2face.tool] [INFO] Stage opened

2022-05-16 13:01:12 [98,276ms] [Error] [gpu.foundation.plugin] RsrcManager timeline semaphore value is invalid, typically a device lost. RsrcManager is unable to delete resources. current value: ffffffffffffffff, next: 22ba
2022-05-16 13:01:12 [98,278ms] [Error] [carb.graphics-direct3d.plugin] HRESULT: 0x80070057
2022-05-16 13:01:12 [98,278ms] [Error] [carb.graphics-direct3d.plugin] CommandList::Close() failed.
2022-05-16 13:01:12 [98,279ms] [Error] [carb.graphics-direct3d.plugin] HRESULT: 0x887a0005, Map() failed.
2022-05-16 13:01:12 [98,280ms] [Error] [carb.graphics-direct3d.plugin] HRESULT: 0x887a0001
2022-05-16 13:01:12 [98,280ms] [Error] [carb.graphics-direct3d.plugin] GPU crash. Device is lost or reset.
2022-05-16 13:01:12 [98,280ms] [Error] [omni.kit.renderer.plugin] A GPU crash occurred. Exiting the application...
Reasons for the failure: a device lost, out of memory, or an unexpected bug.

But I’ve attached the entire log in case I am mistaken.
Hope you can help :-)
kit_20220516_150120.log (337.7 KB)