Windows 10 SDK (November 2015)

The Windows 10 SDK for the November 2015 update of Windows 10 (build 10586) is now available. It can be installed via an optional install with VS 2015 Update 1 or as a standalone installer. This includes DirectXMath 3.08, Direct3D 11.4, Direct3D 12.0, DXGI 1.5, updates to Direct2D/DirectWrite 1.3, and XAudio 2.9.

GitHub: All of my open source project have new releases to support VS 2015 Update 1 and the Windows 10 SDK (10586): DirectXTK, DirectXTex, DirectXMesh, UVAtlas, Effects11, and DXUT11.

DirectX Developer Runtime: The DirectX Developer Runtime for Windows 10 is an optional feature called Graphics Tools as described in this blog post. When upgrading from 10240 to 10586, the optional feature can be disabled rather than updated, which can be fixed by re-enabling the optional feature. Note that WARP12 is part of the Graphics Tools optional feature as it’s currently intended only for use by developers.

XInput: For UWP, you can continue to use the XInput 1.4 API but need to change from linking to xinput.lib to xinputuap.lib. Alternatively, you can make use of the GamePad class in DirectX Tool Kit which uses the new Windows.Gaming.Input API. See XInput and Windows 8.

XAudio: With the Windows 10 SDK, if you are linking with xaudio2.lib you are linking against XAudio 2.9 and should build your application using _WIN32_WINNT=0x0A00. If you want to use XAudio 2.8 with the Windows 10 SDK, you need to set _WIN32_WINNT=0x0602 or _WIN32_WINNT=0x0603 and link against xaudio2_8.lib. See XAudio2 and Windows 8 for more details.

VS 2013 Users: As with the past few releases, the Windows 10 SDK only integrates with the latest Visual Studio, VS 2015. You can use the Windows 10 SDK with VS 2013 by using the props attached per this Visual C+ Team Blog.

Samples: As with the Windows 10 SDK RTM, official Windows samples are hosted on GitHub: Windows-universal-samplesWindows-classic-samples, Windows-driver-samples. Additional Direct3D 12 samples can be found in DirectX-Graphics-Samples. See also DirectX SDK Samples Catalog.

Related: Windows 10 SDK RTM, Windows 10 Anniversary Update SDK

Comments (2)

  1. Guest says:

    Happy New Year.

    I see you prefer to use UNICODE version of function.

    In case of DirectX 12 it is very small reason use TCHAR, TEXT and so on macros in a project?

  2. Generally all applications should use UNICODE. With Windows 8 Store apps, this was strongly enforced with most ANSI versions of Win32 APIs removed. With universal Windows apps for Windows 10, a number of ANSI versions of Win32 APIs were added back, but mostly for strings that were never shown to the user (i.e. internal object names, etc.). You can still use ANSI strings for debug output, but the general expectation is that you should be using UNICODE by default.

Skip to main content