You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AMD GPU Services (AGS) library provides software developers with the ability to query AMD GPU software and hardware state information that is not normally available through standard operating systems or graphic APIs. Version 4.0 of the library includes support for querying graphics driver version info, GPU performance, Crossfire™ (AMD's multi-GPU rendering technology) configuration info, and Eyefinity (AMD's multi-display rendering technology) configuration info. AGS also exposes the explicit Crossfire API extensionand additional extensions supported in the AMD drivers for DirectX 11.
4
+
The AMD GPU Services (AGS) library provides software developers with the ability to query AMD GPU software and hardware state information that is not normally available through standard operating systems or graphic APIs. Version 4.0 of the library includes support for querying graphics driver version info, GPU performance, Crossfire™ (AMD's multi-GPU rendering technology) configuration info, and Eyefinity (AMD's multi-display rendering technology) configuration info. AGS also exposes the explicit Crossfire API extension, GCN shader extensions, and additional extensions supported in the AMD drivers for DirectX 11 and DirectX 12.
5
5
6
6
In addition to the library itself, the AGS SDK includes several samples to demonstrate use of the library.
7
7
8
-
**Note:** Shader extension support has been temporarily removed while we wait for an updated driver that fixes certain issues.
AGS now returns a lot more information from the GPU in addition to exposing the explicit Crossfire API and other extensions for DirectX 11. Highlights include the following:
13
+
AGS now returns a lot more information from the GPU in addition to exposing the explicit Crossfire API and other extensions for DirectX 11. Version 4.0 also exposes GCN shader extensions for both DirectX 11 and DirectX 12. Highlights include the following:
16
14
17
15
* The initialization function can now return information about the GPU:
18
16
* Whether the GPU is GCN or not
@@ -22,6 +20,9 @@ AGS now returns a lot more information from the GPU in addition to exposing the
22
20
* New explicit Crossfire API
23
21
* Provides the ability to control resource transfers between GPUs in Crossfire configuration in DirectX 11
24
22
* Allows improved performance in multi-GPU configurations
23
+
* New GCN shader extension support
24
+
* DirectX 11 and DirectX 12
25
+
* Requires Radeon Software Crimson Edition 16.9.1 (driver version 16.40) or later
25
26
* AGS provides access to additional extensions available in the AMD driver for DirectX 11:
26
27
* Quad List primitive type
27
28
* UAV overlap
@@ -45,6 +46,8 @@ In addition to the three samples included in this repo, there are other samples
45
46
*[CrossfireAPI11](https://github.com/GPUOpen-LibrariesAndSDKs/CrossfireAPI11) - a larger example of using the explicit Crossfire API
46
47
* The CrossfireAPI11 sample also comes with an extensive guide for multi-GPU: the *AMD Crossfire guide for Direct3D® 11 applications*
47
48
*[DepthBoundsTest11](https://github.com/GPUOpen-LibrariesAndSDKs/DepthBoundsTest11) - a sample showing how to use the depth bounds test extension
49
+
*[Barycentrics11](https://github.com/GPUOpen-LibrariesAndSDKs/Barycentrics11) - a sample showing how to use the GCN shader extensions for DirectX 11
50
+
*[Barycentrics12](https://github.com/GPUOpen-LibrariesAndSDKs/Barycentrics12) - a sample showing how to use the GCN shader extensions for DirectX 12
48
51
49
52
### Premake
50
53
The Visual Studio projects in each sample's `build` directory were generated with Premake. To generate the project files yourself (for another version of Visual Studio, for example), open a command prompt in the sample's `premake` directory (where the premake5.lua script for that sample is located, not the top-level directory where the premake5 executable is located) and execute the following command:
0 commit comments