Hey everyone!
I’m posting this topic because I’ve seen way too much outdated information on this topic. My company itself paid for a Unity pro license before we started developing with Kinect, because everywhere you look it says you need it to develop for the Kinect. Be it some forum posts or video tutorials, they often mention this.
I’m not 100% sure on where this information came from originally, but I think it had to do with Unity requiring a Pro seat for you to import custom Unity Packages way back in the day. The base GitHub repo we used to start learning the Kinect specifies that you need Unity Pro to import plugins and packages, so I think that’s where it came from.
Anyway - it doesn’t seem like you need it for ANY of the Kinect’s features, and the sources that say you do date back to 2014 (at least the ones I’m aware of).
I hope this is helpful to any of you who might be using the Kinect!
2 Likes
Way, wayyyyyyyyy back. Like you said, that was over ten years ago! 
There was a time up until some version of Unity 5.x where Unity wouldn’t allow you to load a DLL unless you had a Pro license. It had nothing to do with any Kinect specific features, just that DLL restriction. Which I believe you could even work around (or did not apply) if the DLL code did not make use of the UnityEngine API.
Worth mentioning: back then that was most likely Kinect v1, perhaps a very early SDK and tutorial for Kinect v2 at most. But for years now we have Azure Kinect aka v4 - I mention this in case you’re unaware and are starting to target an out-of-production (and technically outdated) hardware.
There are also assets on the store that help you interface with or enhance Kinect workflows so you don’t need to resort to decade-old (and probably long abandoned) libraries.
1 Like
You just need right files in right folder just copied and pasted