error finding Kinect 2

[Rob Baddorf]

I have a Kinect 2 connected (Windows 8.1 recognizes it)
When I launch the Brekel demo it can't see it and warns me that the Kinect 2 is not connected.
Anyone know what to do?

Thanks in advance.

[Rob Baddorf]

FYI: I get the message "No Kinect v2 Found" in most every window within the Brekel Pro Body 2 v2.01

[Brekel]

Does your machine meet the minimum requirements?

Especially:

USB 3.0 port, Intel and Renesas chipsets only! (others brands may or may not work)

And:

DirectX 11 capable GPU

For example one of these:

Intel HD 4400 integrated display adapter

ATI Radeon HD 5400 series

ATI Radeon HD 6570

ATI Radeon HD 7800 (256-bit GDDR5 2GB/1000Mhz)

NVidia Quadro 600

NVidia GeForce GT 640

NVidia GeForce GTX 660

NVidia Quadro K1000M

There is a link to the Kinect v2 Configuration Verifier in the help menu which should check your hardware for compatabilities.

There are also links to the Trouble Shooting Guide and Microsoft forums with lots of information on this topic.

[Motion Story]

Along the same lines as Rob.

Kinect v2 Configuration Verifier errors only on USB 3 connection, everything else is okay.

I have USB 3.0 ports on motherboard, so this is puzzling. 

Has anyone had the same thing happen?

[Brekel]

The Kinect v2 drivers only support Intel and Renesas USB3 chipsets at the moment, others brands may work but it's not guaranteed.

Note that the official Microsoft forums are probably the best and quickest source for hardware help:

https://social.msdn.microsoft.com/Forums/en-US/home?forum=kinectv2sdk

There's a troubleshooting and common issues guide here:

https://social.msdn.microsoft.com/Forums/en-US/20dbadae-dcee-406a-b66f-a182d76cea3b/troubleshooting-and-common-issues-guide?forum=kinectv2sdk

[Jarrod Linton]

The Microsoft forums have been the most help.

Having installed a new USB 3 card and which is SATA powered. The MS forums said that it was probably the ASMedia USB 3.0 eXtensible Host Controller, which was right so disabling this in control panel meant that the Renesas USB 3.0 Hub could connect. 

So I Windows shows in Devices that the Kinect 2 is connected to USB 3.0. The Kinkect Configuration Verifier still shows a red cross for USB, but displays depth and colour working in a live feed.

The sample SDK program 'Body Basic' now works and picks up and displays my IK motion. But Brekel Body Pro 2 crashes on opening. 

This is the print from the crash.

Problem Event Name: APPCRASH

  Application Name: ProBody2.exe

  Application Version: 0.0.0.0

  Application Timestamp: 54f4828c

  Fault Module Name: ProBody2.exe

  Fault Module Version: 0.0.0.0

  Fault Module Timestamp: 54f4828c

  Exception Code: c0000005

  Exception Offset: 000000000000c780

  OS Version: 6.3.9600.2.0.0.256.48

  Locale ID: 1053

  Additional Information 1: e938

  Additional Information 2: e93893afc918378339b83b702db6acd6

  Additional Information 3: 8f44

  Additional Information 4: 8f4439d79271702a7176a72d853a7606

[Brekel]

What does the little black console box say?

[Motion Story]

The SDK Connection Verifier app was open. So was thinking that this caused the crash. With a restart Body Pro 2 did open but didn't pick up the Kinect. While it was open a software update window popped up and I reinstalled Body Pro 2 again. Restarted and reopened and it connected. Great!!

The console printed an OK on the for connections when I had the crashes. The update seems to have fix this.

[Brekel]

Good to hear that fixed it for you and you're up and running now.

Enjoy!

[kasim...@yahoo.co.uk]

I'm having the following appear when I try the Pro Body c2 trial: 

Initialize Color:         EEOR finding sensor

And in the app itself all windows display the test "No Kinect v2 Found"

It cant be a hardware incompatibility becuase my Kinect V2 sensor works fine with apps like 3D Builder for scanning. Latest Microsoft SDK is installed

Any help appreciated finding a fix

[kasim...@yahoo.co.uk]

Actually this has magically been rectified now, opened and close the software a couple of times and now it picks the sensor up!

Thanks

[Brekel]

Weird, but glad to hear it sorted itself out :)

[Xavier Matia Bernasconi]

I'm having a similar problem

the sensor cannot be found, it works in the kinect studio or in unreal engine, but not in Pro Body 2.0 (the trial version)

the 3 red led are on and the xbox logo is lit too on the sensor.

what is strange is that if i restart kinect studio after pro body, the kinect is not recognized anymore, only if i start it before pro body 2

any idea what i could do to fix?
thanks

Xavier

[Brekel]

Hmmm, that's really weird.

Does manually installing vcredist_x64.exe from this following official Microsoft link help?
https://www.microsoft.com/en-us/download/details.aspx?id=40784

Do the examples from the SDK work properly: C:\Program Files\Microsoft SDKs\Kinect\v2.0_1409\bin\

InfraredBasics-D2D.exe

BodyBasics-D2D.exe

[Sean McHugh]

Hi fellow-brekellers

I too have a problem getting the Trial edition of Face Pro v2 to recognize a Kinect - in this case a Kinect for Windows v2.

I have USB 3.0 and other programs (Reallusion's iClone 6 Pro) recognize and accept the Kinect v2 data when it is running.

Perhaps it is a problem only with the trial version?

I cannot find any USB 3.0 Hub controllers that guarantee to use a Renesas chipset. My MoBo runs Etron eXtensible HCI v 1.0 

System Specs

Homebuild ASRock Z68 Extreme4 (with USB 3.0),  i7-2600K @3.4Ghz , 16 Gb RAM, 5.5Tb HDD, Palit GeForce GTX 750 Ti running DX 12.0; Win 10 Pro (64-bit) + Samsung S24D300H 1920X1080 + spare 1680X1050.

Any suggestions?

Thanks for that.

Sean McHugh

[Xavier Matia Bernasconi]

ok

I didn't fix it, but it works now if pro body is the first software that i open that connects to kinect.
If i open underal engine with a plugin that connects to kinect or any of the demo programs, pro body doesn't find the sensor.

this is the case though with the demo programs too, I can't seem to be able to run infrared and bodybasics one after the other.

It seems something is not released properly and other applications cannot connect to the kinect after that.

I need to restart the machine and then i can reconnect to the kinect.

Xavier

[Brekel]

Hmmm that's weird and not something I can reproduce here unfortunately.

It is possible that it's due to your USB3 chipset though.

Officially only the Intel and Renesas chipsets are supported by the Microsoft Kinect v2 drivers.

It is possible that others work but have issues with two apps accessing the same sensor simultaneously. (which indeed should work)

You mention "USB3.0 Hub", does that mean your sensor is not connected directly to your computer?

If so you may want to try connecting it directly and see if that helps.

[Sean McHugh]

Hi Brekel

Thanks for your reply. I appreciate it.

Unfortunately I won't be doing any experiments for a while. The Windows 10 crashed while I was hot-swapping the keyboard to a USB 2.0.

The crash was insanely successful. It has taken my OS back to 2011, and deleted not only Windows 10 but also all backups.

I have a lot of work to do before I can try your interesting program suite again. 

I hope you will take my troubles into account next time I am in a position to ask for a download?

The USB 3.0 hub I mentioned is really just a HCI controller but it sometimes gets called a hub in the documentation. It is a part of the Z68 Extreme4 MoBo.

I think Win 10 may have had a problem with the twin monitors and the multiple users on this machine. But it is only a guess: I had to delete all but one user and one monitor to get the Win 7 SP 1 update to install.

Give me a few weeks and I'll be back.

Regards all round

Sean McHugh