![]() If this option is not used, the last 1000 lines of logging are saved to the default location:Ĭ:\Users\*username*\Documents\3DMark\Log\3DMark.logĮnable per workload debug logging. Logging does not affect the benchmark score. Save the benchmark progress log to the given file. Send results to online service (default off). Only used in combination with -online=on for submitting a result online or -export for exporting a result to an XML file. 3dmdef file to manually select a GPU to be used. Apply the desired LUID to the “dxgi_adapter_luid” field of the appropriate test-specific. This is useful for determining the desired adapter LUID for DirectX 12 tests that support manually selecting the GPU. List the available graphics adapters and their LUIDs. Use 0 to loop the test indefinitely until the run is manually ended.Įnable SystemInfo Monitoring (default off). Set the number of times to loop benchmark. Specifies the XML file that defines the tests and settings to be used. Removes all 3DMark DLCs and settings filesĬhanges the language of the application, for example, de-DE. ![]() Install a standalone 3DMark DLC file from the given path.Ĭhanges the destination path for downloaded DLCs and other runtime files. ![]() You can only run 3DMark from the command line with a valid Professional Edition license. Register 3DMark with the given license key. When on or off is omitted with an option, on is assumed. Use the following command-line option to work around this issue: start /max 3DMarkCMD.exe Options You may have problems running DirectX 12 tests from a PowerShell terminal due to the way PowerShell works with full-screen DirectX 12 applications. Type the command below in the Command Prompt window and press enter. With 3DMark Professional Edition, you can run 3DMark benchmarks from the command line. Solution home 3DMark 3DMark command line guide Run 3DMark benchmarks from the command line
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |