What could be happening is *if* Naturalpoint stipulated that using the TrackIR SDK mean *exclusive* support for TrackIR devices only (eg. Kinect would be disallowed later)
I'll just nip this in the bud right now.
While it's true that our API only supports our own hardware, we did not stipulate that Microsoft couldn't also implement their own Kinect API in addition to the TrackIR API.
Thank you for correcting me Seth. I tried to point out the possibility of why Flight might not have TrackIR support (which is annoyoing for all of us that have one [or more] TrackIR units about). As I said, using your interface is exceedingly easy - so technical reasons are really no excuse for Microsoft.
I hope I also made it clear that my understanding of the situation with the Eagle Dynamics series was only based on what was posted in the ED forums and I was extrapolating from A (the DCS situation in the past, according to their forums) to a possible reason for B (MS Flight). As you know, the community has a long memory of what goes on, even if things (eg. Naturalpoint's position) are now different with regard to exclusivity.
Fortunately we are now blessed with TrackIR 64-bit support, even if ED has not re-started work implementing an alternative tracking interface. It would be very nice if you could clarify whether they are still prohibited from doing so by their agreement with Naturalpoint (so we can ask for this work to be resumed), but it is fair enough if you refrain from commenting.