So we’ve now added builds of the AGS binary library that are linkable with Visual Studio projects built with /MT and /MD, used to select a particular CRT. We’ve listened to feedback about how difficult it can be to integrate the binary AGS libs into your games, and while we can’t open the source code to AGS to allow you to integrate it from source, we canvassed developers to figure out what pre-built binaries would be most useful to provide.

Version 5.1 is a partly developer-focused update to AGS 5. The new API gives you the ability to leave markers around your D3D11 API calls, helping you narrow down exactly what interaction with the driver caused the problem. Sometimes your game or app can interact with the driver in a way that causes it to crash or TDR. Using the agsDriverExtensionsDX11_WriteBreadcrumb() API, you can put in place a strategy for debugging driver issues more easily. Lastly, we’ve also added support for breadcrumb markers in D3D11. We also changed how you get access to extensions under DX12, requiring you to create your GPU device using agsDriverExtensionsDX12_CreateDevice(), instead of the normal D3D12CreateDevice() call you’d make to D3D.

App registration lets you give more information about your game or application to our driver, which can then use that (ideally unique) information to better support the game or app if we need to make driver-side changes to help things run as efficiently and correctly as possible. Version 5.2 adds support for app registration in DirectX 12.

Directx 11 sdk