Share via

GetRenderTargetData - Backbuffer and Render Target

  • Article

This automated test verifies that the IDirect3DDevice9::GetRenderTargetData method in Microsoft® Direct3D® 9 can be used to extract the contents of back buffers and basic render targets.

The test first creates the source and destination surfaces. The test then cycles through various surface formats and usage specifications. If either surface cannot be created, that configuration is skipped. After the surfaces are created, the render-target surface is filled with a textured quad. Next, the source is copied to the destination with the GetRenderTargetData method, and a surface comparison is performed to verify that the two surface contents are the same.

This topic applies to the following test jobs:

  • GetRenderTargetData - Backbuffer and Render Target

  • GetRenderTargetData - Backbuffer and Render Target (WoW64)

Test details

   
Specifications
  • Device.Graphics.AdapterRender.MinimumDirectXLevel
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows Server 2016 (x64)
  • Windows 10, client editions (Arm64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 8
Category Compatibility
Timeout (in minutes) 480
Requires reboot false
Requires special configuration false
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

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.

  • Microsoft DirectX® 9.0 or later

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting Device.Graphics Testing.

More information

This section will include test-related content that may not aid the tester in running or troubleshooting the test, but is information that is good to know, but not necessary for running the test.

This test validates the functional and operational specifications for the IDirect3DDevice9::GetRenderTargetData method. The GetRenderTargetData method provides a way to copy the contents of a render-target surface to a system-memory surface. There are several restrictions on the source and destination surfaces that you must meet for this copy to succeed:

  • The source surface must be a regular render-target surface, or a specific level of a render-target texture (MIP map or cube texture).

  • The source must be POOL_DEFAULT and D3DMULTISAMPLE_NONE.

  • The destination surface must be either an off-screen plain surface, or a texture (MIP map or cube) that is created with POOL_SYSTEMMEM.

  • The source and destination surfaces must be the same dimension and format.

The following table shows the matrix of surface combinations that this test covers, and the command options that the test uses to select the type of surface.

Surface Offscreen plain MIP-map texture Cube texture

Back buffer

-grtdbb

-grtdbbt

-grtdbbct

Render target

-grtdrt

-grtdrtt

-grtdrtct

MIP-map texture

-grtdts

-grtdtt

-grtdtct

Cube texture

-grtdcts

-grtdctt

-grtdctct

 

Command syntax

Command option Description

Getrendertargetdata.exe -grtdbb -grtdbbt -grtdbbct -grtdrt -grtdrt -grtdrtt -grtdrtct -M:1 -dx9 -whql -logclean

Runs the test job, including options for specific surfaces. For more information about which option to use, see the table earlier in this topic.

Note

   For command line help for this test binary, type /h.

 

File list

File Location

Configdisplay.exe

<[testbinroot]>\nttest\windowstest\tools\

D3d10ref.dll

<[testbinroot]>\nttest\graphics\d3d\support\

D3d11ref.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dcompiler_test.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dref.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support

D3dref8.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dref9.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx10_test.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx11_TEST.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx8d.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx9_TEST.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

Fpstate.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\utility\

Getrendertargetdata.exe

<[testbinroot]>\nttest\

Modechange.exe

<[testbinroot]>\nttest\windowstest\graphics\d3d\utility\

TDRWatch.exe

<[testbinroot]>\nttest\windowstest\graphics\

Vbswap.x

<[testbinroot]>\nttest\windowstest\graphics\d3d\conf\

 

Parameters

Parameter name Parameter description
MONITOR Index of display output to target with test
MODIFIEDCMDLINE Additional command line arguments for test executable
LLU_NetAccessOnly LLU Name of net user
ConfigDisplayCommandLine Custom Command Line for ConfigDisplay. Default: logo
TDRArgs /get or /set