● Стресс тест графического процессора, создающий близкую к предельной нагрузку;
● Режим автоматического обнаружения ошибок изображения, вызванных нестабильностью GPU, в рендеринге тестовой сцены; мониторинг температуры графического процессора в ходе теста;
● Возможность автоматической и ручной настройки сложности тестирующего шейдерного кода;
● Поддержка конфигураций SLI;
● Тест надежности видеопамяти, построенный на API универсальных вычислений CUDA.

Main Revamped the communication between the test for reactivity and robustness. It also paves the way for the upcoming Linux edition
Main Introducing the "Combined" test allowing you to launch several tests in parallel - some make a lot of sense, some don't ( Running CPU and Memory at the same time is a BAD idea as they will compete for resources - using CPU RAM is advised )
Main Greatly improved OCCT's startup time, especially on older setups
Main OCCT will now do its best to work around some silly antivirus locking temp files or purging them before use.
Ui Updated the underlying technology of the UI ( Major update if there's any ) which led us to reimplement a lot of stuff - paving the way for the future. CPU Usage of the UI is lower than ever
Ui Updated brand identity and looks for the UI, to reflect our new brand identity. OCCT has never been looking so amazing !
Ui You can now chose between Direct3D and OpenGL as a renderer option. Direct3D is the default, but suffers from flickers with Nvidia cards due to a bug in either Nvidia drivers or Windows that hasn't been fixed for more than a year now. It's the same bug as Chrome. You can switch to OpenGL to avoid those, but the UI will use more RAM sadly.
Monitoring Updated Monitoring Engine
Monitoring Added VRAM usage support to the top monitoring bar
Monitoring Fixed: You can now disable the "Physical memory used" sensor in the table
Settings Coolermaster collaboration ended sadly - the option for the coolermaster skin has been removed and won't be present in v13 anymore. Maybe it will come back in the future !
Cpu Split the CPU test to CPU and CPU RAM ( CPU Small (v12) => CPU (v13), CPU Medium and Large (v12) => CPU RAM (v13)). This is to better outline which component the test is actually testing
MemoryBenchmark Introduced a new mode for the Latency Bandwidth benchmark, testing a lot of different data set points, going up to 1GB. You'll now have full curves for identifying breakpoints !
Report Major update to the HTML report : graphics, technology, memory used
Report The HTML report graph tooltip will now properly report values exactly at the hovered point ( previous hovers were off by a few points )
Report Fixed a memory leak that could occur in the HTNL report when comparing

Портативная версия предоставлена разработчиком, работает без инсталляции на ПК.