1 – Overview

New Vulkan and OpenGL demos (based on GeeXLab engine) have been added in the 3D demos panel:

All GeeXLab demos can now be launched using the command line:
GpuCapsViewer.exe /demo_win_width=1920 /demo_win_height=1080 /demo_fullscreen /run_gxl_demo=vk_shadertoy_geomechanical /benchmark_log_results /benchmark_duration=10000 /demo_msaa=0 /vk_gpu_index=0

Command line parameters can be found in the _run_geexlab_benchmark.bat file available in GPU Caps Viewer folder. The benchmark results are saved in a CSV file (_gxl_benchmark_results.csv).

Another change brought to GPU Caps concerns the UAC (User Account Control) execution level that has been reset to the default value (as invoker). The previous UAC level (administrator) didn’t work well with launching demos via the command line.

All Vulkan code has been recompiled with latest Vulkan headers (v1.0.45).

>> Update: 2017.06.29 <<

GPU Caps Viewer 1.34.4.0 is a maintenance release and comes with a better Vulkan support. The Vulkan field in the GPU tab is now updated according to the selected GPU. The Vulkan plugin of the GeeXLab SDK comes with an improved support of AMD and Intel GPUs and resizing of Vulkan demos has been fixed.

>> Update: 2017.04.29 <<

GPU Caps Viewer 1.34.3.1 is a maintenance release and comes with a new VK-Z version. VS2015 generates some strange patterns in the 32-bit version of VK-Z and no matter the way I compile VK-Z, the 32-bit version of VK-Z is still flagged as infected by some antivirus. The 64-bit version of VK-Z is clean so I just replaced the 32-bit version by the 64-bit one. GPU Caps Viewer has been updated to execute VK-Z x64 on Windows 64-bit only…

>> Update: 2017.04.26 <<

GPU Caps Viewer 1.34.3.0 is a maintenance release and improves the detection of recent AMD Radeon GPUs (RX 580, RX 570, RX 480 and RX 470). GPU Shark has been updated to version 0.9.11.4. VK-Z has been updated to version 0.6.0.5 32-bit (it has been recompiled with other compilation options in order to avoid false positive detection with antivirus. I really don’t understand this pesky problem!).

>> Update: 2017.04.16 <<

GPU Caps Viewer 1.34.2.1 is available with VK-Z 0.6.0.3. The previous 32-bit version of VK-Z was detected as infected by some antivirus scanners. Now VK-Z 32-bit is clean for Nod32, Avira, Avast, Kaspersky, AVG, Norton, and MacAfee.

>> Update: 2017.04.14 <<

GPU Caps Viewer 1.34.2.0 adds the support of NVIDIA TITAN Xp. GPU Shark and VK-Z have been updated to their latest versions.

>> Update: 2017.04.01 <<

GPU Caps Viewer 1.34.1.0 improves the detection of AMD Radeon GPUs in some systems that include Intel iGPU + AMD Radeon GPU. A new GeeXLab/OpenGL demo has been added (Alien Corridor).

2 – Dowloads

2.1 – Portable version (zip archive – no installation required):

2.2 – Win32 installer:

For any feedback or bug report, a thread on Geeks3D forums is available HERE.

3 – What is GPU Caps Viewer?

GPU Caps Viewer is a graphics card information utility focused on the OpenGL, Vulkan, OpenCL and CUDA API level support of the main (primary) graphics card. For Vulkan, OpenCL and CUDA, GPU Caps Viewer details the API support of each capable device available in the system. GPU Caps Viewer offers also a simple GPU monitoring facility (clock speed, temperature, GPU usage, fan speed) for NVIDIA GeForce and AMD Radeon based graphics cards. GPU data can be submitted to an online GPU database.

4 – Changelog

Version 1.34.4.0 – 2017.06.29
! Vulkan field in GPU tab is now updated according to the selected GPU.
* fixed a bug in the VK-Z output window (there was garbage at the end).
* fixed minor bugs in the Lua kx framework (v1.4) used by GeeXLab demos.
! improved the Vulkan plugin (GeeXLab SDK) with better
support of AMD and Intel GPUs.
! updated with GeeXLab SDK libs.

When I run GPUCapsViewer v1.34.0 3D Demos the OpenCL demos on Win7, it would pop out error “OpenCL GPU not supported on the selected platform”. Then I switched to “OpenCL” sheet, its default setting is “1: Intel(R) OpenCL”. After changed manually to “2. AMD Accelerated Parallel Processing”, the OpenCL demos could run successfully.
But on Win10 OS, the GPUCapsViewer OpenCL demos didn’t need this manual setting, why?

Open Gl demos shows me that i haw rx 560 i haw 460
Open CL GPU 4D Quaterian Julia goes and then stops on second whit some black stripes.
And Vulkan also some times stuters 60-100fps
And pc makes noize when there is 1000fps

Hello, I have a GTX 1070. Is it normal or why does one of the 3D Demos always seem hang when I try to change the window size and then stay black? The framecount is huge, it should be easily able to do a change like that unless the software forbids it (or there is some problem). In the Vulkan toy Geomechanical even the driver crashed when I tried to change the window size although the card generally runs stable with its settings, also in Furmark and Unigine (even parallelly).

Could it be a simple driver issue? Neither the GPU load nor Power Consumption are maxed, though GPU-Z there is some Reliance Voltage cap active. It is probably related to framecount, similar as in Furmark where lowering MSAA raises frames and lowers MHz, but here it is actually a completely average load. It crashed again when touching the window in Geomechanical.

I don’t know what you have against my completely serious and valid comments and question. Besides, I seriously think some of the demos are buggy. I can change Seascape and Geomechanical into fullscreen without problem, but I can’t adaptively change the window size without frames going exteremely low, the window turning black, and the demo usually craashing. Even with default GPU settings.

And your 4D Quaternion Julia Set demo also was clearly buggy when I had an RX 480, But I suppose this is a really old demo, and I have had similar problems with a MSI Kombustor test like it (it just looks completely wrong).

Maybe you should give a warning for the demos or do some more testing with them.

Yes Vulkan demos have some issues related to window resizing. I recently fixed these issues in my framework and the next update of GPU Caps should be ok. For OpenCL demos, yes I know they have some bugs with radeon GPUs. I will try to look at them, but they are old…

Hi JeGX
we found if we run capsviewer 1.34.3.1 through command_line , the opencl test will failed and capsviewer will carsh, but the new vulkan test all passed.
we run the same opencl test from capsviewer GUI , all test passed.
so we check the diffrerent of command-line and GUI.
we found in the command-line mode, we use the paramater /bench_log_results to save log, and capsvirewer try to save the result to bench_result.csv but failed.
so capsviewer crashed.