This is a repository for the test suite for DirectX Tool Kit for DirectX 11 on GitHub.
git clone https://github.com/Microsoft/DirectXTK.git
git clone https://github.com/walbourn/directxtktest.git Tests
git clone https://github.com/Microsoft/DirectXTK.wiki.git wiki
DirectXTK_Tests_Desktop_2015, DirectXTK_Tests_Desktop_2017, DirectXTK_Tests_Desktop_2019
These cover the entire library for Windows desktop (aka Windows classic) including DirectXTK for Audio using XAudio 2.8.
These cover just DirectXTK for Audio using XAudio 2.7 for down-level support on Windows 7 which requires the legacy DirectX SDK to build, and the legacy DXSETUP to deploy the required DLL.
DirectXTK_Tests_Desktop_2015_Win10, DirectXTK_Tests_Desktop_2017_Win10, DirectXTK_Tests_Desktop_2019_Win10
This covers the GamePad component which uses the Windows 10
Windows.Gaming.Input WinRT API, as well as DirectXTK for Audio using XAudio 2.9 for Windows desktop (aka Windows classic).
This covers GamePad, Keyboard, and Mouse when using the WinRT APIs as well as graphics components for Universal Windows Platform (UWP) apps.
When using UWP on Xbox One, it's recommended you set the option Treat UWP apps as games by default in the Device Portal for your development & testing Xbox One consoles. See this blog post for more information.
They are built using individual
x_XboxOneXDK_2017.sln files. Note also that the 2015 and 2017 versions use the same intermediate file folders so you should only build one set or the other.
Command line options
The PC versions of the test suite support the following command-line switches:
-forcewarpForces the use of the WARP software device. Normally this only gets used as a fallback if no hardware is found.
-minpowerWhen run on Windows 10 April 2018 Update (Version 1803) and built using VS 2017 (15.7 update) with the Windows 10 SDK (17134), the test suite will prefer the use of
DXGI_GPU_PREFERENCE_HIGH_PERFORMANCEdevices by default. If this switch is provided, then it will prefer the use of
DXGI_GPU_PREFERENCE_MINIMUM_POWERinstead. This primarily impacts hybrid graphics systems to force selection between AMD/NVIDIA and Intel Integrated devices.
-adapter:nForces the use of a particular adapter at index
n(0-based). If the adapter index is invalid, you'll end up with WARP.