Nuitrack SDK cannot find my Orbbec Gemini 2

I tested OrbbecViewer.exe and it can successfully capture Color, Depth, IR, Point Cloud data.
Please refer to Figure 1 and 2


I’ve downloaded the latest version of nuitrack-windows-x64.exe, but it can’t find my Orbbec Gemini 2.
Please refer to Figure 3

This is what the device manager shows Orbbec Gemini 2
Please refer to Figure 4
Device Manager

I have used Kinect v2 to test that the Nuitrack SDK can operate normally.
What other pre-settings do I need to do?

Many thanks!

Gemini 2 support is in progress according to the Nuitrack depth sensor page:

Edit: v0.37.8 has just been released with beta Gemini support

Hello, @mavishsieh8313, @gabor.

Thank you for your interest in the Nuitrack. Please, provide us with the following information:

  • OS
  • PID/VID of the problematic sensor(s)
  • Nuitrack version

PID/VID are located here in OrbbecViewer:

Orbbec Viewer image

They can also be found here in windows (there’ll be your sensor instead of the device present on the picture):

Windows device manager image

Hi, @gvr

OS
-CPU:Intel(R) Core™ i5-8300H
-RAM:8.00 GB
-System type:x64
-Version: Windows 10

PID/VID of the problematic sensor(s)
PID:0x0701
VID:0x2BC5

Nuitrack Version
0.37.7

Hey, @mavishsieh8313.

Thanks for the feedback. We’ll mention you here as soon as there’s some news.

1 Like

Hey, @mavishsieh8313.

There’s a little contradiction between the title and the screenshots you have sent. Could you, please, add some details about your sensor by answering the following questions? Why is your sensor named ‘DaBai DCL SN#AUG56300040’? Did you buy it from official Orbbec store?

There’s a picture of how Gemini 2 looks in OrbbecViewer:

images

ours: image
yours: image2

Hey, @mavishsieh8313.

How are you doing? Do you have any feedback on this issue?

Hi @gvr ,

Sorry for the late reply.

We bought Gemini 2 from dealer website.

Dealer YAHBOOM Website

Purchase Website
https://detail.tmall.com/item.htm?id=727469964546&scene=taobao_shop&spm=a1z10.1-b-s.w5003-22651379998.13.246944e1udb8FA

We changed to use a Type-C cable to connect, and it displayed the same device name.

Please check out the picture below.

Hey, @mavishsieh8313.

Thanks for the information. We’re now clarifying some details with the dealer. We’ll let you know if there’s any news.

1 Like