This is a major update that adds Vulkan support to the API Overhead feature test. Benchmark scores are unaffected with the exception of API Overhead feature test, which now produces scores for Vulkan instead of Mantle. New Added Vulkan support to the API Overhead feature test. Use the API Overhead feature test to compare Vulkan, DirectX 12, and DirectX 11 API performance on your PC. The Vulkan test requires compatible video drivers with Vulkan support. Check with your GPU vendor for Vulkan driver support if your hardware is unable to run the test. Note that the Vulkan test replaces the Mantle test found in previous versions of 3DMark. Improved SystemInfo scan time greatly improved on X99 systems. Fixed Fixed an issue that could cause the API Overhead feature test to fail to show a score at the end of an otherwise normal run on some systems. Fixed Time Spy test to properly recover from a corrupted shader cache - if runtime compiled shaders are found to be corrupted, they are deleted and recompiled. Uninstallation also now completely removes the shader cache folder. Fixed a scaling issue that could cause parts of the UI to end up outside the display area on 1080p monitors with 150% DPI scaling. UI will now scale appropriately even on high DPI scaling settings.

This update fixes a GUI issue that resulted in marginally lower than expected scores when starting a test from the Benchmark Details screen in 3DMark versions 2.1.2852 and later. Benchmark runs started from the Home screen or the Command Line were not affected. It is normal for 3DMark scores to vary by up to 3% between runs since there are factors in a modern, multitasking operating system that cannot be completely controlled. With this update, overall scores are expected to increase by up to 0.3%. Scores from the Physics and CPU parts of benchmark tests may improve by up to 2.5%. Scores from this version of 3DMark are consistent with results from previous versions that did not have the GUI issue. Compatibility Added a two-minute timeout to the SystemInfo scan to prevent it from stalling for long periods on some specific systems.

Is your PC ready for VR? Find out with VRMark, the virtual reality benchmark from the developers of 3DMark. The performance required for VR is much higher than for typical PC games. Run VRMark to see if your PC has what it takes to deliver a great VR experience on the HTC Vive and Oculus Rift. VRMark benchmark tests run on your monitor, no headset required. If your PC passes, it's ready for the two most popular VR systems available today.

This is a minor update to fix problems reported by some users. Benchmark scores are not affected with one exception - see the section about Fire Strike Custom runs below for details. Improved SystemInfo module updated to 4.48 for improved compatibility with the latest hardware. The video RAM check that warns if your system may not be able to run a test now accepts extra main RAM beyond the minimum requirement as VRAM for integrated graphics. We've added a DETAILS button to the panel for the Recommended test on the Benchmarks screen to make it easier to find formation and the settings for the test. This is also where you find the option to enable or disable the demo for each test. Fixed Fire Strike Custom run settings Unfortunately, the previous version of 3DMark used an incorrect setting for Fire Strike Custom runs that resulted in slightly lower than expected scores. Fire Strike Custom run results from 3DMark v2.1.2852 should not be compared with this latest version nor with any other version of 3DMark. The standard Fire Strike benchmark run was not affected, nor were Fire Strike Extreme and Fire Strike Ultra. Restored the control for volumetric illumination sample count setting on the Fire Strike Custom run screen, which was missing in the previous version. Fixed the default value for volumetric illumination sample count for Fire Strike Custom runs. In 3DMark v2.1.2852, Fire Strike Custom run used an incorrect default setting of 1.5. This has been reverted to 1.0, which is the correct value for the test. Other fixes Fixed an issue that could prevent the in-app update from working properly. Fixed an issue that prevented Sky Diver from starting on 32-bit Windows. Fixed an issue that caused Time Spy to crash when scaling mode was set to Stretched. Fixed an issue that could cause result parsing to fail on complex systems with lots of devices due to the unusually large data set generated by the SystemInfo scan. Fixed an issue that caused the installation to fail if the unzipped installer content resided in a path that included a folder name with a space. Known Issues Time Spy fails to run on multi-GPU systems with Windows 10 build 10240, but this is not the fault of the benchmark. You must upgrade Windows 10 to build 10586 (“November Update”) or later to enable multi-GPU configurations to work. Installing the 3DMark app and the DLC test data to the same folder is not a supported configuration. The latest version will prevent you from installing both to the same folder. If you currently have 3DMark and the DLC test data installed to the same custom folder you will need to uninstall 3DMark then reinstall the latest version using the full installer.

This major update adds Time Spy, a new DirectX 12 benchmark test. With its pure DirectX 12 engine, which supports new API features like asynchronous compute, explicit linked multi-adapter, and multi-threading, 3DMark Time Spy is the ideal benchmark for testing the DirectX 12 performance of the latest graphics cards. New Added Time Spy Stress Test - a new dedicated Stress Test for high-performing PCs running on Windows 10. Time Spy Stress Test is not available in 3DMark Basic Edition or 3DMark Time Spy upgrade in Steam. Fixed Fixed an issue that could cause all Stress Test runs to end with 0% score. Fixed an issue that could prevent self-update from working (standalone version only). If you are running 3DMark 2.0.2724 or 2.0.2809 Advanced Edition, you need to download and install the full 2.1 installer to update.

This is a minor update that fixes several compatibility issues. Benchmark scores are not affected. Fixed Fixed further compatibility issues with the Steam launcher and some specific operating system configurations that could cause the 64-bit version to refuse to start. Fixed an issue with result file processing that could cause the benchmark to hang with a black screen at the end of a demo or test on some systems.