Blt - Textures
Note This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.
Type: Automated Test
Most of the Microsoft DirectDraw tests (including the Blt - Textures test) are located in Fnddraw.exe. You can run Fnddraw.exe outside of the DCT shell, and select initial 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 visually analyze the blt results. Use the <Pause> key to pause and resume.
Use the <ESC> key to abort a test run. Be patient because some tests are more responsive than others.
This test verifies that graphics adapters correctly perform blts between a variety of texture formats. The tests are broken out by the memory type of the source and destination textures (System, Video, and AGP).
The tests are implemented in Fnddraw.exe and consist of the following specific tests:
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.)
Currently, the test will tolerate a driver that returns DDERR_UNSUPPORTED on the blt call and will 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 pre-determined list of pixel formats. It trusts that the driver will fail the surface creation, if the pixel format is not supported.
To run this test, use the Fnddraw.exe executable file.
- Run Time: 00:01:00
- Log File:
- System Restart Required: No
- Test Category:
- Supported operating systems for Logo or Signature testing:
Windows Server 2008 R2
Windows Server 2003
The test tool requires the following software:
- Supported operating system (see list above).
- Software components included with the device that is being tested.
- DirectX version 7.0 or later
- Hardware Requirements
- Device to be tested
- Computer that meets the minimum software requirements
- Windows keyboard
- Two-button pointing device
- Color display monitor capable of at least 1024 by 768 resolution, 32-bits per pixel, 60 Hz
- Hard drive with a minimum of 20 GB available on partition C:
- Display adapater with DDraw capabilities
There are no specific steps to follow for this test. You should run Fnddraw.exe.
fnddraw.exe dd_txblt.pro -r -c -p"m%MONITOR%"
Replace the %MONITOR% parameter with a 1-based index that corresponds to the display that you are 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.
Microsoft DirectX SDK (version 7.0 or later)
Build date: 9/14/2012