Sprites and textures · microsoft/DirectXTK12 Wiki · GitHub

In this lesson, we will cover the basics of creating a texture from a bitmap file, and then rendering it using a 2D sprite with various drawing options.

First create a new project using the instructions from the previous lessons: Using DeviceResources and Adding the DirectX Tool Kit which we will use for this lesson.

A sprite is a bitmap rendered at some location on the screen. For Direct3D, this requires making use of:

A committed resource which is the texture containing the bitmap image pixel data for rendering.

The shader resource view descriptor created in a resource descriptor heap which describes the properties of the texture resource.

A sampler which describes how the GPU should handle various aspects of reading the texture data for rendering (such as image filtering and/or tiling of the bitmap).

This can be a static sampler in the root signature or a heap sampler referenced in a sampler descriptor heap.

Additional Direct3D objects are also required for drawing (vertex buffer, index buffer, pipeline state object, and root signature), but in this tutorial these are handled by SpriteBatch.

Some additional Direct3D objects are also required for uploading the texture data (upload heap committed resource, fence, command allocator, and command list) but in this tutorial these are handled by ResourceUploadBatch.

Finally, some 'in-flight' memory related to constant buffer views and dynamic vertex buffers are also required, and these are managed by GraphicsMemory.

Start by saving cat.png into your new project's directory, and then from the top menu select Project / Add Existing Item.... Select "cat.png" and click "OK".

In the Game.h file, add the following variable to the bottom of the Game class's private declarations (right after the m_graphicsMemory variable you already added as part of setup):

In Game.cpp, add to the TODO of CreateDeviceDependentResources after where you have created m_graphicsMemory:

In Game.cpp, add to the TODO of OnDeviceLost where you added m_graphicsMemory.reset():

Build and run the application which will still not be displaying anything but the cornflower blue window, but will have a texture loaded.

If you get a runtime exception, then you may have the "cat.png" in the wrong folder, have modified the "Working Directory" in the "Debugging" configuration settings, or otherwise changed the expected paths at runtime of the application. You should set a break-point on CreateWICTextureFromFile and step into the code to find the exact problem.

In DirectX 12 the application is responsible for managing video memory, including uploading resources from 'shared memory' to 'dedicated video memory'. The ResourceUploadBatch class is a helper for managing this process. When the End method is called, it creates a C++11 "future" which allows the upload process to happen potentially on another thread. You must wait on the C++11 future at the end of CreateDeviceDependentResources to ensure it completes the upload before continuing. For more, see Wikipedia and cppreference.com.

In the Game.h file, add the following variables to the bottom of the Game class's private declarations:

In Game.cpp, modify TODO of CreateDeviceDependentResources to include after resourceUpload.Begin and before the resourceUpload.End:

In Game.cpp, add to the TODO of CreateWindowSizeDependentResources:

If using the UWP template, you should also add m_spriteBatch->SetRotation(m_deviceResources->GetRotation()); to handle display orientation changes.

In Game.cpp, add to the TODO of OnDeviceLost:

In Game.cpp, add to the TODO of Render:

Build and run, and you should get the following screen:

You'll note that setting the descriptor heap is left to the caller. This allows the application to use their own heaps instead of the DescriptorHeap class. You can freely mix and match heaps in the application, but remember that you can have only a single texture descriptor heap and a single sampler descriptor heap active at any given time. To change active heaps, you should End the current batch, call SetDescriptorHeaps, and then call Begin to start a new one.

One thing you should notice is that the edges of the cat look strange with a bit of white outline. The problem here is that the cat.png file's alpha channel is straight alpha (i.e. the pixels are of the form (R,G,B,A)). The default behavior of SpriteBatch, however, is to assume you are using premultiplied alpha (i.e. the pixels are of the form (R*A, G*A, B*A, A)). There are many reasons why using premultiplied alpha is superior, but for now we can fix this mismatch by changing our use of SpriteBatch to use straight alpha blending instead by supplying our own ID3D11BlendState object. We'll make use of the CommonStates class to provide one of the built-in blend state objects.

In Game.cpp, modify the creation of SpriteBatchPipelineStateDescription in CreateDeviceDependentResources:

Build and run again, and you'll get a nice clean cat:

Rather than use a PNG and the Windows Imaging Component (WIC) to load the texture, a more efficient thing for us to do is to make use of a DDS file instead. A DDS file is a container for all kinds of Direct3D resources including 1D and 2D textures, cubemaps, volume maps, arrays of 1D or 2D textures or cubemaps each optionally with mipmaps. It can contain a wide-array of pixel formats and hardware-supported 'block-compression' schemes to save on video memory usage at runtime.

Visual Studio has a built-in system for converting images to DDS as part of the build process, which you can read about here.

For this tutorial, we will instead make of use of the DirectXTex texconv command-line tool.

Then run the following command-line:

Then from the top menu in Visual Studio select Project / Add Existing Item.... Select cat.dds and click "OK".

Now will return to Game.cpp in the CreateDeviceDependentResources and change our use of CreateWICTextureFromFile to CreateDDSTextureFromFile:

Note that since we used the option -pmalpha, we should also make sure we change back using premultipled alpha because our "cat.dds" has premultiplied alpha in it.

In Game.cpp, modify SpriteBatchPipelineStateDescription in CreateDeviceDependentResources:

Build and run we are rendering our 'clean' cat with premultiplied alpha:

Now that we have our cat rendering, we can start to animate it. Here's a simple rotation where we are using the cosf function to give us a time-varying value from -1 to 1.

In Game.cpp, modify the TODO of Render:

Build and run to see the cat spinning.

We can scale a sprite's size as well. Again, we are using cosf to give us a time-varying value between -1 and 1.

In Game.cpp, modify the TODO of Render:

Build and run to see the cat growing and shrinking.

We can modify the color of the sprite with a tint as well:

In Game.cpp, modify the TODO of Render:

Build and run to see a green-tinged cat.

With the optional source-rectangle parameter, we can tile a sprite.

In the Game.h file, add the following variables to the bottom of the Game class's private declarations:

In the Game.cpp file, add to TODO section of CreateDeviceDependentResources:

modify the creation of SpriteBatchPipelineStateDescription:

and then change

to

In Game.cpp, add to the TODO of OnDeviceLost:

In the Game.cpp file, modify in the TODO section of Render:

Build and run to see the sprite as an array of 4x4 cats.

By default SpriteBatch uses a static sampler that is set to 'linear clamp'. In order to do the tiling, we had to override that setting by providing a descriptor-heap sampler instead. The CommonStates object provides a descriptor heap with pre-defined sampler descriptors that can be used for this purpose.

CommonStates also provides static methods for getting the equivalent 'static sampler' description when setting up custom root signatures such as StaticLinearWrap(). Using these methods doesn't require making the CommonStates descriptor heap 'active'.

Using the optional destination rectangle instead of a 2D position, we can stretch a sprite.

In the Game.h file, add the following variable to the bottom of the Game class's private declarations:

In the Game.cpp file, add to the TODO section of CreateWindowSizeDependentResources:

In the Game.cpp file, modify in the TODO section of Render:

Build and run to see the sprite blown up

Our last exercise for this lesson is rendering a sprite as a full background image. Start by saving sunset.jpg to your project directory, and then from the top menu select Project / Add Existing Item.... Select "sunset.jpg" and click "OK".

In the Game.h file, add the following variables to the bottom of the Game class's private declarations:

and change

to

In Game.cpp, add to the TODO of CreateDeviceDependentResources to include after resourceUpload.Begin and before the resourceUpload.End:

In Game.cpp, add to the TODO of CreateWindowSizeDependentResources:

and then modify the m_origin initialization back to:

In Game.cpp, add to the TODO of OnDeviceLost:

In Game.cpp, modify the TODO section of Render to be:

Build and run to see our cat drawing over a sunset background.

If we were only drawing the background (i.e. a single 'sprite' that fills an entire viewport), then using BasicPostProcess's Copy operation is faster than SpriteBatch.

SpriteBatch can be used to draw "filled color rectangles" extremely easily. Just use a 1x1 white texture, and draw it as a sprite with optional tinting. This allows you to easily batch-up solid rectangles with other sprite drawing as well.

The various techniques demonstrated in the DirectX 11 tutorials all apply to DirectX 12 SpriteBatch as well such as animated sprites, scrolling backgrounds, and sprite sheets.

SpriteBatch can perform sorting of the sprites in a number of different modes. We've used the default sortMode of SpriteSortMode_Deferred for Begin. If drawing with lots of different textures, you should try SpriteSortMode_Texture. If you are making use of the layerDepth parameter to sort your sprites correctly, use SpriteSortMode_BackToFront or SpriteSortMode_FrontToBack. For all these modes, the actual drawing does not happen until you call End--or you exceed the internal vertex buffer size. If you use SpriteSortMode_Immediate, then the sprite is drawn as soon as you call Draw.

SpriteBatch can 'flip' the texture image at runtime using SpriteEffects_FlipHorizontally, SpriteEffects_FlipVertically, or SpriteEffects_FlipBoth. The default effects parameter for Draw is SpriteEffects_None.

When drawing lots of different sprites, having to load hundreds of individual texture files is inefficient and potentially wastes video memory. One solution is to pack the sprite images into a single (or a few) textures and then render parts of them using sourceRectangle for Draw.

The SpriteBatch class has a 'rotation mode' setting which can be used to handle device orientation changes for Universal Windows Platform (UWP) apps, or just for special effects. You call SetRotation with one of the DXGI_MODE_ROTATION settings which controls the final view transformation to flip the output an extra 90 degrees, 180 degrees, or 270 degrees. It defaults to no extra rotation with DXGI_MODE_ROTATION_IDENTITY.

The transformationMatrix parameter to Begin lets you provide a custom transformation for the sprite renderering. This is combined with the viewport-based final view transform, but if you use SetRotation( DXGI_MODE_ROTATION_UNSPECIFIED ) this will be disabled. The default value for this parameter is the identity matrix.

You can use custom texture sampler states for special effects utilizing texture addressing. You can also achieve a 'pixel art' look by using CommonStates::PointClamp.

Since all DirectX 12 hardware is at least Hardware Feature Level 11.0, you can count on BC4, BC5, BC6, and BC7 compression format support, as well as texture and cubemap arrays, for your texture resources.

Next lesson: Drawing text

DirectX Tool Kit docs CommonStates, DescriptorHeap, DDSTextureLoader, RenderTargetState, ResourceUploadBatch, SpriteBatch, WICTextureLoader

Direc3D 11 Textures and Block Compression

Premultiplied alpha Premultiplied alpha and image composition Premultiplied alpha in XNA Game Studio 4.0