Command-Line Parameters for the Direct3D Mobile Driver Comparison Test (Windows CE 5.0)
The Direct3D Mobile Driver Comparison Test runs the tux –o –d D3DM_DriverComp.dllcommand line by default. You can modify the behavior of the Direct3D Mobile Driver Comparison Test by editing the command line for the test. To specify one or more of the following optional command-line parameters for this test, use the –c command-line parameter. The -c parameter forces Tux to pass the specified string into the test module. For more information about how to edit the command line for a test, see Editing the Command Line for a Test.
If a test case fails after running the test with the default command line, run the Direct3D Mobile Driver Comparison Test with thetux -o -d D3DM_DriverComp.DLL -x <test_case_ordinal> –c "/i /o"command line. This command line instructs the test to not delete images after the test completes. For information about the test cases for the Direct3D Mobile Driver Comparison Test, see Test Cases for the Direct3D Mobile Driver Comparison Test.
The following table shows the command-line parameters for the Direct3D Mobile Driver Comparison Test.
| Command-line parameter | Description |
|---|---|
|
Instantiates the driver to test and the Direct3D Mobile reference driver for each test case, and then compares rendered output.
This behavior is the default behavior for the Direct3D Mobile Driver Comparison Test. The command-line parameters /t1, /t2, and /t3 are mutually exclusive. |
|
Instantiates only the driver to test for each test case, and then compares the output to previously stored output from the Direct3D Mobile reference driver.
The command-line parameters /t1, /t2, and /t3 are mutually exclusive. |
|
Instantiates only the Direct3D Mobile reference driver for each test case and stores output for future use.
The command-line parameters /t1, /t2, and /t3 are mutually exclusive. |
|
Specifies the path for images to compare, including images generated by the driver to test, images generated by the Direct3D Mobile reference driver. The test also stores at this location the images that show differences between the images compared.
Include a trailing backslash (\) character in the value that you specify for this parameter. |
|
Renders into a window that is 50 pixels by 50 pixels.
The command-line parameters /e1, /e2, /e3, /e4, /e5, /e6, and /e7 are mutually exclusive. |
|
Renders into a window that is 220 pixels by 176 pixels.
The command-line parameters /e1, /e2, /e3, /e4, /e5, /e6, and /e7 are mutually exclusive. |
|
Renders into a window that is 176 pixels by 220 pixels.
The command-line parameters /e1, /e2, /e3, /e4, /e5, /e6, and /e7 are mutually exclusive. |
|
Renders into a window that is 320 pixels by 240 pixels.
The command-line parameters /e1, /e2, /e3, /e4, /e5, /e6, and /e7 are mutually exclusive. |
|
Renders into a window that is 240 pixels by 320 pixels.
The command-line parameters /e1, /e2, /e3, /e4, /e5, /e6, and /e7 are mutually exclusive. |
|
Renders into a window that is 640 pixels by 480 pixels.
The command-line parameters /e1, /e2, /e3, /e4, /e5, /e6, and /e7 are mutually exclusive. |
|
Renders in full-screen mode.
The command-line parameters /e1, /e2, /e3, /e4, /e5, /e6, and /e7 are mutually exclusive. |
|
Creates the window with the WS_OVERLAPPED style.
The command-line parameters /w1 and /w2 are mutually exclusive. |
|
Creates the window with the WS_POPUP style.
The command-line parameters /w1 and /w2 are mutually exclusive. |
|
Validates a locally hooked driver instead of the default system driver. The Direct3D Mobile Driver Comparison Test uses the RegisterSoftwareDevice function before running a test case, and uses D3DMADAPTER_REGISTERED_DEVICE at the time that the CreateDevice function is called. |
|
Specifies that the images from the driver being tested and the Direct3D Mobile reference driver not be deleted during the cleanup phase of the test. |
|
Specifies that the images that show differences between the compared images not be deleted during the cleanup phase of the test. |
|
Displays command-line parameters for the test. |
See Also
Direct3D Mobile Driver Comparison Test | Test Cases for the Direct3D Mobile Driver Comparison Test
Send Feedback on this topic to the authors