Share via

WGF11 Precision (WoW64)

  • Article

This automated test ensures that when shaders specify the minimum partial precision flag (8, 10, or 16-bit) that IHVs do not use a lower precision for calculations. For example, the shader specifies 16-bit but the IHV uses 10-bit.

This topic is applicable to the following test cases:

  • WGF11 Precision

  • WGF11 Precision (WoW64)

  • WGF11 Precision FL9.3

  • WGF11 Precision FL9.3 (WoW64)

Note

   Using higher precision than the minimum specified value is valid.

 

Test details

   
Specifications
  • Device.Graphics.AdapterRender.D3D11PartialPrecision.D3D11CoreE
Platforms
  • 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) 2
Category Compatibility
Timeout (in minutes) 120
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.

Troubleshooting

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

For troubleshooting information, see Troubleshooting Device.Graphics Testing.

This test will always return Pass if precision is handled correctly, or return Fail if not. To review test details, review the test log from the Windows HLK Manager.

If the partial precision test fails, try setting your driver to ignore the partial precision flags. If that passes, then it means that when you are attempting to follow the partial precision flags, you are using a lower precision than what the shader specified. E.g. The shader asked for 16-bit minimum, but you are using 8-bit or 10-bit. If you ignore the partial precision flags, and it still fails, ensure other conformance tests pass because the test relies on things like "sample" working correctly.

More information

The partial precision group in WGF11Precision.exe ensures that when shaders specify the minimum partial precision flag (8, 10, or 16-bit) that IHVs do not use a lower precision for calculations. For example, the shader specifies 16-bit but the IHV uses 10-bit. Using higher precision than the minimum specified value is valid.

Command syntax

Command option Description

WGF11Precision.exe

Runs the test jobs.

Note

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

 

File list

File Location

Configdisplay.exe

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

D3d11_1sdklayers.dll

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

D3d11ref.dll

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

D3d11sdklayers.dll

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

D3dcompiler_test.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\

TDRWatch.exe

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

WGF11Precision.exe

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

 

Parameters

Parameter name Parameter description
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