Orbbec azurkinect body tracking crashes

I am getting crashes across 2 computers with body tracking. Application just quits, this is error I am getting in event viewer:

Faulting application name: vvvv.exe, version: 2025.7.0.1, time stamp: 0x68760000
Faulting module name: k4abt.DLL, version: 1.1.2.0, time stamp: 0x627d5fb4
Exception code: 0xc0000005
Fault offset: 0x0000000000297918
Faulting process id: 0x1ec4
Faulting application start time: 0x01dc271726985e49
Faulting application path: C:\Program Files\vvvv\vvvv_gamma_7.0-win-x64\vvvv.exe
Faulting module path: C:\Program Files\Azure Kinect Body Tracking SDK\tools\k4abt.DLL
Report Id: e2b850e9-e36f-484b-ac3d-abd493c9c128
Faulting package full name:
Faulting package-relative application ID:

These are my settings for the node:

I have a theory what could be the problem. I think that when VVVV + Fuse is initializing something on GPU, it interferes with the Orbbec trying to work with GPU and it throws some access violation. I think this happens especially if there is some change happening with fuse - turning on patch that is in If region, etc.. - So if you are running a relatively static app that has everything loaded its ok.

I am getting this when I open patch, and can reliably reproduce. If femto/tracking is enabled while I am prewarming all fuse patches, I get crash. But if its disabled while they are loading, its ok.

For now I just switched to using CPU - the tracking is much slower, but its not crashing

huh. and you’ve also tested the other processing modes? any gpu mode has that issue?

I tested GPU and DirectML and both were throwing this error and crashing, I can try the other modes as well, but so far first priority was to have stable option which I have now.

@StiX any chance you could give the Cuda option a spin and see if it behaves the same? beware: requires cuda 11.4 to be installed as mentioned here: NuGet Gallery | VL.Devices.AzureKinect.Femto 1.8.1

unfortunately do not have orbecc anymore as it was part of just one project I did last year