The new EULA, for the Kinect For Windows, is equally flawed. Specifically this (Section 2, Subsection (ii)): “…that it is intended for use only with the Kinect for Windows sensor.” It is explicit that code cannot be developed for the XBOX 360′s Kinect unless it is for test purposes only.

And this (Section 3): “You may not work around any technical limitations in the software”

That’s why I still use the open source drivers. But who knows, Microsoft could do something similar to Sony and claim that it is illegal to modify hardware you own. I’d then be forced to use the new Kinect and their SDK. Hopefully it doesn’t come to that.

What kind of restrictions of the Microsoft Kinect SDK that forced you to switch to the open source drivers? I assume that you are referring to the new Kinect for Windows SDK that can be used for commercial use.

Yes, there are drivers available from several users for direct integration. I have modified my post accordingly. I should note that I don’t actively use this code any more.

congratulations on the project, I try to look at it and I will comment

Maybe 7 hours? Most of the side missions are weak sauce fetch quests. I left the game before the Green Lantern stuff came through so I don’t know how long those would take.

My response below:
There are 3 places I can see creating problems, and please pardon me if I misunderstand something:
“The Axis is a vertical vector…..”
You mention that this is a vertical vector to the old and new vectors between shoulder and elbow. Is this vector created in some way by the new and old vectors or did you just mean you are rotating your elbow-> shoulder vector relative to a stationary vertical axis? The way I read your comment was that you create a new vertical axis each time you need to calculate the position of your elbow->shoulder bone. The vertical axis you choose should remain constant. In my case, I always rotate relative to the global UP axis of my system: Vector3(0,1,0).
“And the angle can I get from the Angle between the actual Vector…..”
The function you mention, cos(alfa) =v_new * v_old / |v_new|*|v_old|, isn’t a signed angle. Example: The angle between Vector(0,1,0) and Vector(1,1,0) equals the angle between Vector(0,1,0) and Vector(-1,1,0). Does that make any sense? Basically you need a function to calculate the angle between 2 vectors relative to another vector. I don’t have the formula handy but take a look at my function ‘AngleBetween’ in https://github.com/Jerdak/KinectDaemon/blob/master/Unity3D/Client.cs
“Than I multiply the rotationmatrix with the last rotationmatrix and the Dll send this matrix to the renderer”
Make sure the order multiplication is correct. From the Rotation_Matrix wiki: “For n greater than 2, multiplication of n×n rotation matrices is not commutative.” A * B != B * A. Additionally, you shouldn’t need to multiply your rotation matrices each frame. Say my arm is straight down at my side and I raise it to the side by 45 degrees. Then I rotate it another 12 degrees to the side. It’s safer to simply create a new rotation matrix for the 57(45+12) degrees rather than multiplying 2 rotation matrices together.