Cuda 10.1 support

[derivativerobmc]

Is there a timeline for updating the library to Cuda 10.1? We're switching over to Visual Studio 2019 and my understanding is that cuda 10.0 has problems with visual studio 2019.

[yijiew]

All our development and sample code projects are using VS2019 and we didn't see any problem. Could you clarify what kind of issue you will hit by using Cuda 10.0 dll in VS2019?

[derivativerobmc]

host_config.h in the Cuda 10.0.130 SDK has a line that checks for the MSC_VER and currently throws an error if it's greater than or equal to 1920 with the message that only VS 2013 - 2017 are supported

[yijiew]

Thanks for clarification. But for the body tracking SDK, only the cuda binaries are needed. Customers shouldn't need to link to Cuda SDK at all.

[derivativerobmc]

We're not using it for the body tracking, but we do use the Cuda SDK a lot in other parts of our project. We've disabled it for the moment to get things working, but we'll need it in the long run.

I noticed the onnxruntime 1.2 says it upgraded to cuda 10.1 about a week ago. Will this get carried over to the kinect relatively soon?

thanks for the help.

[derivativerobmc]

Any word on updating the body tracking sdk to use a newer version of cuda? Other components in our project require 10.1 and we don't want to be shipping multiple versions.

[maruta]

I'm experiencing a problem with k4abt_simple_3d_viewer.exe on a Windows machine with RTX 3080, where the tracking window doesn't appear and not even a log file is generated.

I'm beginning to suspect that a lower version of the bundled CUDA is the cause, as it works when I remove the RTX 3080 and install a much older GT710, and it works even with the CPU options specified.

For your information, the same binary works correctly on another Windows machine with Quadro RTX 5000 (Turing architecture).

So far, I'm not sure if that's a reason to upgrade the CUDA version or if it's a problem with my RTX3080 unit, I'm writing here in the hopes that someone else experiencing the same phenomenon will find it.

[qm13]

We have had several reports of issues with the RTX 3080. The issue is likely with CUDA version which is an ONNX Runtime dependency. We are working with the ONNX team to make sure this is addressed in the next release of the Body Tracking SDK which is targeted for end of October / early November.

[chrisnovello]

+1 having the same problem with k4abt_simple_3d_viewer.exe as @maruta, also on rtx 30 series, also had same binary working on a different machine & gpu. runs (very slowly) on this current machine if I execute with the CPU only mode

additionally, seeing a freeze upon trying to init the unit with an Unreal plugin that uses the sdk, which might be related (same plugin was also working on other machine)

eager for new release and to see if 30 series helps give a boost to skeleton tracking

[datee]

Can confirm this issue also, on a computer with RTX 3090 the k4abt_simple_3d_viewer does not open the tracking window.
It just stops. No crash but just nothing happening. CPU mode works fine.

When compiling and testing the examples (simple_cpp_sample) ..its the same.. stops at this line :
k4abt::tracker tracker = k4abt::tracker::create(sensor_calibration);

Really need this, hope a fix is on the way! :)

[L4Z3RC47]

Can confirm this issue also, on a computer with RTX 3090 the k4abt_simple_3d_viewer does not open the tracking window.
It just stops. No crash but just nothing happening. CPU mode works fine.

When compiling and testing the examples (simple_cpp_sample) ..its the same.. stops at this line :
k4abt::tracker tracker = k4abt::tracker::create(sensor_calibration);

Really need this, hope a fix is on the way! :)

Confirmed here as well. RTX 3090.

@yijiew or @qm13 any updates on ETA for the next release?

[VegetableWithChicken]

Who can tell me, has this problem been solved and what needs to be updated. I updated to cudn10.1, but it has no effect.
Do I need to move the CUDN DLL library to bianary replacement of body tracking file ？？
#1423

[qm13]

Currently investigating issue.

[L4Z3RC47]

We have had several reports of issues with the RTX 3080. The issue is likely with CUDA version which is an ONNX Runtime dependency. We are working with the ONNX team to make sure this is addressed in the next release of the Body Tracking SDK which is targeted for end of October / early November.

@qm13 is there a new target date for the next release?

[damaza]

I'm experiencing a problem with k4abt_simple_3d_viewer.exe on a Windows machine with RTX 3080, where the tracking window doesn't appear and not even a log file is generated.

I'm beginning to suspect that a lower version of the bundled CUDA is the cause, as it works when I remove the RTX 3080 and install a much older GT710, and it works even with the CPU options specified.

For your information, the same binary works correctly on another Windows machine with Quadro RTX 5000 (Turing architecture).

So far, I'm not sure if that's a reason to upgrade the CUDA version or if it's a problem with my RTX3080 unit, I'm writing here in the hopes that someone else experiencing the same phenomenon will find it.

The same problem with RTX3070

[L4Z3RC47]

All 3000 series cards are affected. Hoping we can get an ETA soon. I have commercial applications that could really use this!!!

…

On Dec 24, 2020, at 5:22 PM, xiaomaza ***@***.***> wrote:  I'm experiencing a problem with k4abt_simple_3d_viewer.exe on a Windows machine with RTX 3080, where the tracking window doesn't appear and not even a log file is generated. I'm beginning to suspect that a lower version of the bundled CUDA is the cause, as it works when I remove the RTX 3080 and install a much older GT710, and it works even with the CPU options specified. For your information, the same binary works correctly on another Windows machine with Quadro RTX 5000 (Turing architecture). So far, I'm not sure if that's a reason to upgrade the CUDA version or if it's a problem with my RTX3080 unit, I'm writing here in the hopes that someone else experiencing the same phenomenon will find it. The same problem with RTX3070 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[VegetableWithChicken]

Currently investigating issue.

i am also very worried. Please ,please tell me the completion data !
3Q

[jenyaone]

Currently investigating issue.

are there any updates on this? please let us know.

[Lt23live]

We are also having this issue, RTX 3080 series. Microsoft needs to address this.

[L4Z3RC47]

ping @qm13

[Lt23live]

@qm13 has there been any updates?

[AquaLamp]

Thank you. I am eagerly awaiting the results of your investigating issue.

[damaza]

@qm13

[L4Z3RC47]

@qm13 any news? This ticket seems to revolve around onnxruntime support of CUDA 10.1 however onnxruntime has supported both cuda 10.2 and cuda 11 since release 1.5.1
I assume that this is more than just a simple runtime issue then but given this is a major blocker on current gen hardware it would be great to get some deeper feedback on what the issue investigation has revealed and what/if there is a timeline for an update.
Thank you!

[UnaNancyOwen]

@qm13 Currently, the market is moving to GeForce 30XX generation products, and GeForce 20XX/10XX generation products have come to end of sales. NVIDIA has announced the 30XX generation products for laptops. All desktop/laptop on the market will soon be replaced by 30XX generation GPU.
This is a very serious problem for businesses. In fact, we are having trouble procuring new PC that deliver to our customers for work. Please, hurry up with this task (update ONNX Runtime to CUDA 11.x, or support DirectML provider). Thanks!

[L4Z3RC47]

@qm13 Currently, the market is moving to GeForce 30XX generation products, and GeForce 20XX/10XX generation products have come to end of sales. NVIDIA has announced the 30XX generation products for laptops. All desktop/laptop on the market will soon be replaced by 30XX generation GPU.
This is a very serious problem for businesses. In fact, we are having trouble procuring new PC that deliver to our customers for work. Please, hurry up with this task (update ONNX Runtime to CUDA 11.x, or support DirectML provider). Thanks!

#1481 (comment)

Per @qm13 looks like we should see an update around mid next month (usual caveats apply)

great news!

[jaymimc]

We have had several reports of issues with the RTX 3080. The issue is likely with CUDA version which is an ONNX Runtime dependency. We are working with the ONNX team to make sure this is addressed in the next release of the Body Tracking SDK which is targeted for end of October / early November.

Sorry, know i have also listed this on another ticket but it suggested it was closed. As this is still an open ticket, is there any update on when SDK, CUDA and Body Tracking working with NVIDIA 3xxx cards?

[qm13]

Upgraded to CUDA 11.1

[AswinkarthikeyenAK]

Hi Guys,
Can anyone confirm if the body tracking is working fine without any issues with the RTX30xx graphic card,please?
I am planning to buy a desktop with the RTX3070 and I wanted check before I could purchase the desktop.
Thanks for your feedback !!

[lewkoo]

I can confirm that it works fine on RTX 3070 whereas before it didn't. This is on bare-metal Ubuntu 18.04.
See screenshot below as proof.

[AswinkarthikeyenAK]

Hi @lewkoo,
Thanks for the information

[AhmedMedhat]

After upgrading the body tracking library to v1.1, the k4abt_simple_3d_viewer example runs on RTX 3090 (CUDA Version: 11.2), however it prints the following message before creating the tracking window:

2021-04-17 21:15:30.444827715 [W:onnxruntime:K4ABT_ORT_Environment, cuda_execution_provider.cc:1885 GetCapability] CUDA kernel not found in registries for Op type: Sign node name: Sign
2021-04-17 21:15:30.446831171 [W:onnxruntime:K4ABT_ORT_Environment, fallback_cpu_capability.h:140 GetCpuPreferedNodes] Force fallback to CPU execution for node: Shape__40

@qm13 What does this message mean? Does it fallback to CPU processing? @lewkoo did you get similar message when running on RTX 3070?
Thanks for the efforts,

[lewkoo]

After upgrading the body tracking library to v1.1, the k4abt_simple_3d_viewer example runs on RTX 3090 (CUDA Version: 11.2), however it prints the following message before creating the tracking window:

2021-04-17 21:15:30.444827715 [W:onnxruntime:K4ABT_ORT_Environment, cuda_execution_provider.cc:1885 GetCapability] CUDA kernel not found in registries for Op type: Sign node name: Sign
2021-04-17 21:15:30.446831171 [W:onnxruntime:K4ABT_ORT_Environment, fallback_cpu_capability.h:140 GetCpuPreferedNodes] Force fallback to CPU execution for node: Shape__40

@qm13 What does this message mean? Does it fallback to CPU processing? @lewkoo did you get similar message when running on RTX 3070?
Thanks for the efforts,

I got identical message when running k4abt_simple_3d_viewer on 18.04 Ubuntu with CUDA 11.2. Possibly due to this.

AFAIK, it doesn't fallback to CPU processing, at least not entirely. nvidia-smi still shows a process and GPU is experiencing some additional load. From the error message, I can wild guess that it is off loading body shape detection to CPU, while everything else is still running on GPU but this is just a guess. However, our applications that use body tracking seem to perform just as they used to despite these error messages.

[qm13]

@lewkoo That warning is expected. Please see the troubleshooting notes for AKDK in the documentation.

[LU-MING-HUA]

I have a question. I use Win10P RTX3080 to turn on body tracking v1.1.0 but it can’t be displayed. I use CUDA 11.1 according to the article. Is anyone like me? I am a student first contact with Azure Kinect

[ZodiacWind]

I have a question. I use Win10P RTX3080 to turn on body tracking v1.1.0 but it can’t be displayed. I use CUDA 11.1 according to the article. Is anyone like me? I am a student first contact with Azure Kinect

I have encountered the same issue. Could anybody provide some instructions? Really appreciate it.

[VegetableWithChicken]

您好，我一般不常用邮箱，有重要邮件，请QQ我下，谢谢!

[stroombeestje]

I have a question. I use Win10P RTX3080 to turn on body tracking v1.1.0 but it can’t be displayed. I use CUDA 11.1 according to the article. Is anyone like me? I am a student first contact with Azure Kinect

I have encountered the same issue. Could anybody provide some instructions? Really appreciate it.

Same issue here on a 3090RTX

[tinywolf3]

same here. please fix it.