Blt - Textures

This automated test verifies that graphics adapters correctly perform blts between a variety of texture formats. The tests are categorized by the memory type of the source and destination textures (System, Video, and accelerated graphics port [AGP]).

Blt results are compared against a simulation by using either Graphics Device Interface (GDI) operations or the test's internal software blitter. Images are expected to match exactly.

Drivers must support source color key blts between video memory surfaces. Destination color key blts and "space" blts are optional.

This test consists of the following Fnddraw cases:

• Blt_Texture Vid to Vid

• Blt_Texture Sys to AGP

• Blt_Texture Sys to Vid

• Blt_Texture Sys to Sys

Each test runs through a variety of pixel formats, blitting between the memory types that are expressed in the test name. Each blt is a simple copy (no stretching or color keying in this revision of the test). The test expects the destination to perfectly match the source after the blt. Any deviation is considered a failure.

All blts are performed on offscreen surfaces (that is, textures). However, the results are copied to the screen to help you with debugging. (Some details are likely lost in converting from the texture pixel format to the pixel format of the primary surface.)

Currently, the test tolerates a driver that returns DDERR_UNSUPPORTED on the blt call, and does not consider it a failure. This tolerance might change in the future.

Failures might occur from drivers that allow textures to be created in unsupported pixel formats. Drivers should fail the CanCreateSurface function for all non-system memory textures whose pixel formats the drivers do not support. The test blindly runs through a predetermined list of pixel formats. It trusts that the driver will fail the surface creation, if the pixel format is not supported.

This topic applies to the following test jobs:

• Blt - Textures

• Blt - Textures (WoW64)

Test details

Running the test

Before you run the test, complete the test setup as described in the test requirements: Graphic Adapter or Chipset Testing Prerequisites.

In addition, this test requires the following software and hardware.

• DirectX® version 7.0 or later

• Display adapter with DDraw capabilities

Troubleshooting

Before you run the test, complete the test setup as described in the test requirements: Troubleshooting Device.Graphics Testing.

Turn off the screen saver and disable the power management before you run this test. Mode changes and full-screen applications can cause failures, so you should avoid them.

More information

Most of the Microsoft® DirectDraw tests (including the Automatic Stereo test) are located in Fnddraw.exe. You can run Fnddraw.exe outside of the Display Compatibility Test (DCT) shell, and select individual tests. On the Tests menu, click Select Tests.

The test titles that are listed in the DCT shell do not directly match the test names in Fnddraw.exe. In fact, the names in the DCT often refer to a group of Fnddraw tests. You can obtain the Fnddraw test case names from the DCT log file.

You can pause many Fnddraw tests (especially blt-related tests) to give you time to analyze the blt results. Use the Pause key to pause and resume.

Use the Esc key to stop a test run. Be aware that some tests are more responsive than others.

Command syntax

File list

Note  

You do not need Fnswtt.dll to run this test. It is used only for Windows HCK logging.

Send comments about this topic to Microsoft