d3d9-to-11

Graphics concepts mapping

The purpose of this file is to give the reader a general idea of how D3D9 concepts are mapped to D3D11.

In order to understand the Direct3D 9 API, consult the official documentation. The same applies for Direct3D 11’s documentation.

Core (IDirect3D9)

• This is the first interface an application creates, and it is used to query information about the installed GPUs and create logical devices.

• Builds on top of IDXGIFactory, the equivalent interface for D3D11.

Adapter

• Wraps a IDXGIAdapter.

• Represents a physical device. There is a one-to-one mapping of adapters and physical GPUs.

• Also creates a ID3D11Device, since we need it to query capabilties and surface format support.

Device (IDirect3DDevice9)

• Logical view of a GPU.

• Contains a lot of state, it’s owns both a ID3D11Device since it creates resources, but also a ID3D11Context, since it queues commands.

  • A device can be reset (all its state is reset to the default values) at the request of the app.

Surface

• 2D slice of pixels in the same format.

• Can be locked (memory mapped), filled / copied / stretched / etc. All D3D11 operations which apply to 2D subresources also apply to it.

  • A device can be reset (all its state is reset to the default values) at the request of

• For our purposes, it’s holds a reference to a 2D texture (it either owns it, or is a sub-texture).

This site is open source. Improve this page.