https://docs.microsoft.com has no content for the first-generation Kinect sensor. Which uses the Kinect for Windows SDK 1.8.
This SDK and its runtime are readily available for download from Microsoft. However, the SDK documentation has recently been purged. Its return is needed.
Problem:
Kinect v1 aka original Kinect for Windows aka first-generation Kinect content missing. Please note, SDK 2.0 is available but that SDK works on the second-generation Kinect. Completely different hardware and completely incompatible. Therefore, the Kinect for Windows SDK 1.8 is completely distinct and separately needed.
This is a symptom of the Great Darkening. Technology moves forward, yes. However, the archive of documentation for technology is needed for both technical use, backward compatibility, forward compatibility, legacy support, and for future historians/museums. I can appreciate that you have limited resources to update content. Great. Then take the Kinect for Windows SDK 1.8 content, print to PDF, and make that PDF available.
Unfortunately, the waybackmachine doesn't have a working snapshot that I have found. For example, the links to reference docs on this page fail https://web.archive.org/web/20150905084124/https://msdn.microsoft.com/en-us/library/hh855347.aspx
yet I was able to get some others at https://web.archive.org/web/20130526051655/http://msdn.microsoft.com/en-us/library/nuisensor.nuicreatecoordinatemapperfromparameters.aspx
Thank you for creating the issue! One of our team members will get back to you shortly with additional information.
Adding @jemash to help investigate what happened to the linked content.
Has there been any update on these docs? I also would like to have them restored or have a pdf to work with.
Adding an extra voice to the issue... Who deletes docs when the API is still being distributed anyway???
So sad this issue hasn't yet been fixed :/
Still waiting for those docs, I hope this gets resolved soon
Yes, give us full documentation. Just because you stopped producing it and selling it doesn't mean you have to kill the docs. It's just text, it's not like you're out of bytes.
I am currently working on a project using a first generation Kinect and cannot find any SDK v1.8 documentation. Do I have to assume that v2.0 is the same??? Unbelievable that I cannot easily find it with a simple google search.
@Chrisvb99 , 1.8 is completely different than 2.0. The APIs are incompatible and you can't use similar coding.
Without 1.8 API documentation, your project will be very challenging.
@Jemash , would your team please publish a PDF of the docs? Please stop the "Great Darkening"
And now to add to the issue Microsoft has started expunging the 2.0 API documentation!!!
What the BLEEP is wrong with just including the documentation inside the SDK since Microsoft obviously can't be relied upon for archival.
....
Assuming this page for the : CoordinateMapper class hasn't been removed, following the link to documentation for GetCameraIntrinsics ends in a fail
I can also reproduce the failures in the SDK 2.0 documentation on the en-us site
https://docs.microsoft.com/en-us/previous-versions/windows/kinect/dn772971(v=ieb.10)
click "GetDepthCameraIntrinsics"
results in:
"Unable to Service Request"
I did not see this issue assigned to me. I am looking into it now
We are working on moving the missing content to docs.microsoft.com. Thank you for your patience.
Kinect for windows sdk 1.8 has been added back: https://docs.microsoft.com/en-us/previous-versions/windows/kinect-1.8/hh855347(v=ieb.10).
Thanks for the progress update. I clicked randomly in many sections of SDK 1.8 and I see content. 馃檪
Open items of which I'm aware:
It seems to me that the whole C++ reference is still missing. Going to any of the subsections of the C++ reference here take me to a permanently redirected page: https://docs.microsoft.com/en-us/previous-versions/windows/kinect-1.8/hh855364(v%3dieb.10)
@gyurgyma , thanks for surfacing that issue. I didn't notice that in my casual testing.
Can you find the C++ docs in the sibling sections? Meaning...rather than starting at the link you gave for C++, instead start at NUI, Face Tracing, or Dev Kit and then drill down to the C++ interfaces? e.g. https://docs.microsoft.com/en-us/previous-versions/windows/kinect-1.8/hh855366(v=ieb.10)
PDF download has been enabled and is available for both 1.8 and 2.0 SDK. The missing topic you are seeing (GetDepthCameraIntrinsics method) might be trickier and is being looked into.
@diablodale, yes, it looks like I can simply drill down into it. I'm not sure how I didn't manage to figure that out. The PDF also looks to be complete and can be utilized for what I need. Thanks for pushing on this over the last year. Hopefully in time, it gets fully restored.
@diablodale The missing topic has been added: https://docs.microsoft.com/en-us/previous-versions/windows/kinect/getdepthcameraintrinsics. This should complete the resolving of the issues you reported. Please let us know if this can be closed now. Thanks!
It's great that the content is accessible once more - the ideal fix to the originally posted problem would however be to make http://go.microsoft.com/fwlink/?LinkId=280210 (the SDK Documentation link installed by the SDK installer) resolve to the 1.8 SDK docs or at least provide a link on that page since otherwise your fix wont be found.
@kexugit hello. I randomly checked some content in the 1.8 and 2.0 SDKs your team uploaded. I found the following. I do appreciate your team returning the content. Personally, it doesn't have to be perfect as long as the content is there somewhere 馃攳馃檪 Because the below are so methodical/regular, I suspect this is a code/transform issue that if resolved will fix globally these issues.
This same pattern repeats in content
IAudioBeam Interface. It should be the IAudioBeam Interface section on page ~150Methods sections - each with duplicate methods.get_AudioBeamMode@diablodale The broken links and duplicated methods that you reported have been fixed.
The duplicated TOC nodes are by-design: we want to avoid a single TOC node being used for both a expendable parent node, and a node with link. In this case, e.g., the "Known Issues" node served as a parent node with a link on MSDN. When migrated to docs.microsoft.com, it became two TOC nodes: an expandable parent node without link , and another child node with link, both sharing the same name.
For the links inside PDF that point to live site, I understand that you prefer in-file links, but unfortunately I don't think we have the resource to improve that at this time. During migration, we preserved the full URLs inside the topics. However, in order to enable in-file links in PDF downloads, those links have to be converted to the relative path of the corresponding markdown source files. The amount of updates required across all migrated content is not something we could accommodate at this point.
@norlesh we are working on updating the fwlink you reported: http://go.microsoft.com/fwlink/?LinkId=280210. It will be updated to point to the landing page of 1.8 SDK documents.
@kexugit, great...and got all you wrote.
I found two issues in the v1.8 docs PDF download
Thoughout the v1.8 PDF download, the blue section headers are empty with only minutes to read. There is no section name, no number of minutes, etc.
Section names/titles. Personally, I don't need the number of minutes.
Given links within docs don't function, can this issue be resolved so that we can better scan and text-search through the doc?
Missing content on the webpage and the corresponding PDF page. Seems a repeating pattern of a class of content. The first link above is interesting in that there are sometimes 1, sometimes 2 missing pieces of content on each line. I suspect these are images that have text of "public", "static", or "property/member".
More examples where these are missing in the PDF on pages 1262, 1279, 1284, 1286, 1293
It's hard to find the matching webpage...because the section titles are missing ;-)
@diablodale will look into fixing the issues you reported.
@norlesh the fwlink you reported has been fixed.
@diablodale The PDF issues you reported have been fixed. The missing content you were seeing were just icons, but they are also added back to the web pages and PDF files now.
Thank you. I don't have any content concerns with v1.8 or 2.0 docs at this time.
Anyone else have webpage or PDF content concerns?
Thank you all for working through this with us!
@kexugit can this be closed now?
Thank you all for working through this with us!
@kexugit can this be closed now?
Yes. But I don't seem to have permission to close it.
Most helpful comment
Still waiting for those docs, I hope this gets resolved soon