Fix #19 and updated DLLs

[ghost]

I added your fix for #19 and updated the DLLs, which didn't work as I expected.
These are the one from here (don't know what was wrong with my build, had this issue).
Hope this one works universally (I don't know if there is much Windows users to test it)

[LauraLaureus]

@BaptisteTheoriz I'm new to OpenFramework and to Kinect v2, can you provide me a guide to the process you did until get the plugin working on Windows?

[ghost]

Hi, sorry for the delay.
I just updated my repository with a Visual Studio example project and I updated the readme file with instructions about how to install drivers etc.
I hope that will help you, and @ofTheo can merge them if it matches its needs.

[LauraLaureus]

Thank you so much for the update @BaptisteTheoriz ^^ I'll check it as soon as i finish to study some code that the Kinect SDK has >.<.

And you don't have to apologize, I understand everyone has a personal life outside Github. ^^

[LauraLaureus]

@BaptisteTheoriz I got the error libusb1.0.dll not found at running time.
Does the .dll that you uploaded work only in Win32? Intel OpenCL needs to compile in x64.
I did instal the libusbK as you state in the instructions of your fork.

EDIT: I added the path to libusb-1.0.dll (AKA ......\addons\ofxKinectV2\libs\libusb\lib\vs) to project settings Linker\General\ Additional Library Directories and now it works.

[mattfelsen]

Hi @BaptisteTheoriz & @LauraLaureus. Thanks for your work on this! I'm trying to get this running but having some issues. I followed the install instructions (libusbK via Zadig, installed CUDA v8, added the env variables) and can get the app to compile. However, I get this exception when running from VS:

Exception thrown at 0x00007FFF3DCEA74A (igdrcl64.dll) in example.exe: 0xC0000005: Access violation reading location 0x0000000000000994.

If there is a handler for this exception, the program may be safely continued.

which happens after executing this line;

err = clGetPlatformIDs(0, NULL, &numPlatforms);

Some searching indicated it might be an admin privileges thing, and I noticed that running the app, either as an adminstrator or not, directly out of the File Explorer doesn't produce that exception, but also doesn't work either - I just get a blank window at that point.

I'm running on Win10 with VS2015 on a computer with an Nvidia GTX 1060. Any thoughts on things to look into? I'll probably see if I can get the libfreenect2 running as a starter...next year :) What versions of CUDA & VS and which GPU did you get things working with?

Thanks & happy new year y'all!

[LauraLaureus]

I haven't working with CUDA for a year, but I think it's different than OpenCL and the statement that trigger that error is from OpenCL because it has the "cl" prefix.
I don't know if you install CUDA you install together OpenCL, but I only know that OpenCL runs on CUDA based NVIDIA GPU.

I get the example running using Intel OpenCL, since my GPU is Intel's, on Windows 10 + Visual Studio Community 2015.

Sorry, if i'm not helpful u.u And Happy New Year!

[mattfelsen]

Hey @LauraLaureus, thanks for getting back. Ah, you're running on Intel – that makes sense. My understanding is that to compile OpenCL on Nvidia you have to install the CUDA SDK - it contains the headers and whatever else for OpenCL – and there's no separate package. Before installing, I got the Cannot find <CL/cl.h> error, but that was resolved after installing, setting the CUDA_INC_PATH and CUDA_LIB_PATH env vars, and rebooting – so I think Nvidia bundles CUDA + OpenCL support together.

Ah well, I looked into the ofProtonect class and will try the OpenGL and/or CPU pipelines to see if I can get those working and with 2 Kinects.

Cheers!

[mattfelsen]

Ok, up and running with 2 Kinects! One issue was my fault, where I changed the libusbK driver on the wrong device (I selected Xbox NUI Sensor (Interface 0) instead of Xbox NUI Sensor (Composite Parent). With that fixed, I was able to get both Protonect.exe (from the libfreenect 0.2.0 release) and the example project here working, though only with the OpenGL (fast) and CPU (very slow) pipelines. The OpenCL pipeline still throws an exception which I haven't tracked down, but the OpenGL pipeline seems to run very fast even with 2 Kinects.

Also, I didn't need to change any linker paths in VS for libusb - it looks like it's set up properly for linking, but does need ofxKinectV2\libs\libusb\lib\vs\libusb-1.0.dll copied into the application's bin folder. Perhaps you can add something about that to readme as well, @BaptisteTheoriz?

Sorry to turn this PR into a debugging session, but at least it's been confirmed working on 3 different Windows setups :) Signing off until next year...

[ofTheo]

@BaptisteTheoriz - I merged in the other PRs from @bakercp @madelinegannon.
Do you think you could re-submit this or open another PR with the dll fixes for Windows against the current master?

The other PRs added quite a few features the add-on was missing.

Many thanks!
Theo

[ofTheo]

closed #39 should take care of this. master should be windows compatible now thanks to @NickHardeman

[brunoimbrizi]

In case anyone runs into the same problem as @mattfelsen with igdrcl64.dll which just happened to me while trying to run ofxKinectV2/example on my laptop:

Exception thrown at 0x00007FFF3DCEA74A (igdrcl64.dll) in example.exe: 0xC0000005: Access violation reading location 0x0000000000000994.

I managed to solve it by updating the Intel Graphics driver from 21.20.xxx to 26.20.xxx
Device Manager > Display adapters > Intel(R) HD Graphics > Properties > Driver > Update Driver