0 No frame data available

[f-rank]

Getting this message all the time.
At least I can tilt the device.
But no luck getting anything to show up. Keep getting the same message.
I used openfl 3.6.1, lime 2.6.2 and hxcpp 3.4.64 and got the ndll and the SDK and drivers just like instructed.
Managed to get VS2012 also.
Bit stomped now, maybe using the wrong haxe lib versions ?

[f-rank]

Got a sample that comes with Kinect Studio going, so unit malfunction seems to be out of the picture. Was worried as the hardware had not been used in years.

[chrisporter]

I'll see if I can compile and run with the libraries you mentioned.

[chrisporter]

Hi I was unable to compile with lime 2.6.2 but could do so with 2.9.1 and the other libraries you mentioned.

Was able to get all streams running.

I get the "o frame data available" message but them it runs fine.

[f-rank]

Thanks for checking, did the lime 2.91 update, regenerated the ndll. The samples don't show up the streams for some reason, still get the "0 frame data available". Then it holds at black, up and down work though and I can see the red dots in the device light up while executing and going blank after execution is terminated. Maybe it is because of the model, I have a 1414 the initial one for xbox model.
I can't trace any further because it is as if everything should be going ok, it just isn't displaying like in your case. Thanks for looking into it anyway.

[chrisporter]

Yes you need to rebuild the ndll. I have the same behaviour with newer versions of openfl, lime and hxcpp as you describe so please try the exact version above and recompile.

On Tue, 2 Jan 2018 at 17:34 f-rank ***@***.***> wrote: Thanks for checking, did the lime 2.91 update, regenerated the ndll. The samples don't show up the streams for some reason, still gettubg the "0 frame data available". Then it holds at black, up and down work though and I can see the red dots in the device light up while executing and going blank after execution is terminated. Maybe it is because of the model, I have a 1414 the initial one for xbox model. I can't trace any further because it is as if everything should be going ok, it just isn't displaying like in your case. Thanks for looking into it anyway. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACnd5ESirxX4YjmVUT4DxQ8u3YWfuBXks5tGmiogaJpZM4ROiXX> .

-- Best regards, Chris

[f-rank]

Ok. Rebuilt the ndll with the same exact version. Still blank. Maybe it is some problem with my windows inst.
Though the kinect dev kit browser is working and am able to execute the .sln even with VS 2017, with a little tweak on the cmath import lib.

[chrisporter]

It sounds like your kinect is fine. I am able to get streams with the above libraries on another machine with VS2013 and VS2015 installed.

Am currently investigating why it doesn't work with later versions of openfl.

[chrisporter]

Hi f-rank,

Checkout the openflNew branch. This fixes the black screen issue with openfl / lime and hxcpp latest versions for me.

[f-rank]

Hi,

checked out the openflNew branch. Generated the ndll. Color, Depth and DepthUserTracking work and display accordingly.

Interaction example: throws a "1" at the top, then a count up do 20 on ListButton.hx:59, then invalid argument. Then "No frame data available".

IR example: throws a "0" at the top then two "No frame data available".

KinectGraphics example doesn't compile with Main.hx:13 Type not found : interactions.Handtype.

Skeleton example prints "0" then "No frame data available" once and it doesn't seem like it is picking the user skeleton up. Shows blank.

This is all with latest openfl, lime, hxcpp versions.

[chrisporter]

Thanks for the update.

I haven't updated IR yet so that's to be expected and I can't even remember what the graphic example was, will check it out.

For skeleton and interactions make sure the kinect can 'see' a good view before you run. Test with kinect explorer to find a suitable position.

I'm getting the same console warnings but both are running.

https://www.dropbox.com/s/gzhiar5aqadrg0u/Untitled.png?dl=0

You can safely ignore the "No frame data available" message. It seems to miss the first frame and then continues fine. If the kinect has an issue after that you will see that message on each frame that is dropped.

[f-rank]

Thanks. Will retry tomorrow, I did have the device a bit too close. Probably that was the issue with it not picking up a recognizable pose to start tracking.

[chrisporter]

I've update the IR stream and removed the misleading KinectGraphics files.