Home

Awesome

AMD Crossfire API Sample

<img src="crossfireapi11/media/Thumbnail.png" width="480" height="284" />

The CrossfireAPI11 DirectX® 11 sample demonstrates how to use the explicit Crossfire API. This driver extension provides the ability to control resource transfers between GPUs in Crossfire configuration in DirectX 11. This allows improved performance in multi-GPU configurations.

The CrossfireAPI11 sample shows how the Crossfire API is used in the context of shadow caching. The sample shows:

The CrossfireAPI11 sample uses the ShadowFX library. For information on ShadowFX, visit the ShadowFX repository: https://github.com/GPUOpen-Effects/ShadowFX

The Crossfire API driver extension is accessed through the AMD GPU Services (AGS) library. For more information on AGS, including samples, visit the AGS SDK repository: https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK

The CrossfireAPI11 sample also comes with an extensive guide for multi-GPU: the AMD Crossfire guide for Direct3D® 11 applications. It describes the Crossfire implementation in AMD drivers and documents the Crossfire API extensions. The information available in the guide is:

Prerequisites

Getting Started

Premake

The Visual Studio solutions and projects in this repo were generated with Premake. To generate the project files yourself (for another version of Visual Studio, for example), open a command prompt in the premake directory and execute the following command:

This version of Premake has been modified from the stock version to use the property sheet technique for the Windows SDK from this Visual C++ Team blog post. The technique was originally described for using the Windows 8.0 SDK with Visual Studio 2010, but it applies more generally to using newer versions of the Windows SDK with older versions of Visual Studio.

The default SDK for a particular version of Visual Studio (for 2012 or higher) is installed as part of Visual Studio installation. This default (Windows 8.0 SDK for Visual Studio 2012 and Windows 8.1 SDK for Visual Studio 2013) will be used if newer SDKs do not exist on the user's machine. However, the projects generated with this version of Premake will use the next higher SDK (Windows 8.1 SDK for Visual Studio 2012 and Windows 10 SDK with Visual Studio 2013), if the newer SDKs exist on the user's machine.

For Visual Studio 2015, this version of Premake adds the WindowsTargetPlatformVersion element to the project file to specify which version of the Windows SDK will be used. To change WindowsTargetPlatformVersion for Visual Studio 2015, change the value for _AMD_WIN_SDK_VERSION in premake\amd_premake_util.lua and regenerate the Visual Studio files.

Third-Party Software

Attribution