GPU Caps Viewer 1.34.0 Released (Updated: 1.34.4.0)

2017/03/27 JeGX

A new version of GPU Caps Viewer (OpenGL, Vulkan, OpenCL and CUDA utility) is available.

1 – Overview

GPU Caps Viewer 1.34.0 adds the support of the latest GeForce GTX 1080 Ti, Radeon RX 580, RX 570 and RX 560 (based on Polaris 10/11 GPUs) as well as Radeon Pro WX 7100, WX 5100 and WX 4100.

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

GPU Caps Viewer 1.34 + new GeeXLab demos

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.

Version 1.34.3.1 – 2017.04.29
! replaced VK-Z 0.6.0.5 32-bit by VK-Z 0.6.0.3 64-bit.
VK-Z 64-bit does not produce false positive with some
antivirus. VK-Z 64-bit is only executed on Windows 64-bit.

Version 1.34.3.0 – 2017.04.20
! improved detection of Radeon RX 580, RX 570,
RX 480 and RX 470.
! updated: GPU Shark 0.9.11.4
! updated: VK-Z 0.6.0.5
! updated: ZoomGPU 1.20.4 (GPU monitoring library).

Version 1.34.2.1 – 2017.04.16
! updated: VK-Z 0.6.0.3

Version 1.34.2.0 – 2017.04.14
+ added support of NVIDIA TITAN Xp.
! updated Radeon RX 560 shader cores.
! updated: VK-Z 0.6.0
! updated with GeeXLab SDK libs.
! updated: GPU Shark 0.9.11.3
! updated: ZoomGPU 1.20.3 (GPU monitoring library).

Version 1.34.1.0 – 2017.04.01
! improves the detection of AMD Radeon GPUs in some systems
that include Intel iGPU + AMD Radeon GPU.
+ added new OpenGL demo (GeeXLab): Alien Corridor (based on this demo).
Command line demo codename: gl21_shadertoy_mp_alien_corridor
! updated: GPU Shark 0.9.11.2
! updated: ZoomGPU 1.20.2 (GPU monitoring library).

Version 1.34.0.0 – 2017.03.25
+ added support of the GeForce GTX 1080 Ti.
+ added support of AMD Radeon RX 580, RX 570 and RX 560.
+ added support of AMD Radeon Pro WX 7100, WX 5100, WX4100,
WX 4150 and WX 4130.
+ added initial support of AMD Polaris 12 and Vega 10 based videocards.
+ added new parameters for launching GeeXLab demos via the command line.
+ added new Vulkan and OpenGL demos (GeeXLab): Vulkan geomechanical (based on this demo), OpenGL rainforest (based on this demo), OpenGL radialblur (based on this demo), OpenGL rhodium (based on this demo), OpenGL cell shading, OpenGL geometry instancing, OpenGL gs mesh exploder.
! set UAC (User Account Control) execution level to as invoker.
! recompiled with latest Vulkan API headers (v1.0.45).
! updated with latest GeeXLab SDK libs.
! updated: GPU Shark 0.9.11.1
! updated: ZoomGPU 1.20.1 (GPU monitoring library).

35 thoughts on “GPU Caps Viewer 1.34.0 Released (Updated: 1.34.4.0)”

PeterYS 2017/03/29 at 04:25

Hi JeGX, I downloaded the V1.34.0, it still didn’t show AMD Radeon Pro WX 7100, WX 4150 and WX 4130 on Win7, but Win10 is ok.
You can refer the link for compared screen captured pic.
https://drive.google.com/open?id=0B6gN-239wF0mOW9fUWw1d1cxR28
Or should I provide what the information to you? THX!!
1. JeGX Post Author2017/03/29 at 11:45
  
  Could you post here or in the forum, the win7 log file of GPU Caps Viewer ?
PeterYS 2017/03/29 at 04:39

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?
janis 2017/04/02 at 09:38

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
Newbee 2017/04/10 at 12:48

Virus Deteted on executable by Panda Antivirus. W32/Exploit.
1. JeGX Post Author2017/04/10 at 16:04
  
  GPU Caps Viewer 1.34.1 is clean:
  
  https://virustotal.com/fr/file/b140abc1eb2283a5691a48b4a7d0da250c915943551d9685442fed80f0c38c72/analysis/
Sora 2017/04/11 at 00:04

VK-Z output button opens a blank screen.
Jorge 2017/04/17 at 17:54

vkz.exe is still flagged as virus by avast, as of version 1.34.2.1.
It seems you didn’t actually fix that issue.
1. Jorge 2017/04/18 at 05:25
  
  And by AVG too.
  Not strange, since AVG is owned by Avast now.
duz 2017/04/20 at 16:03

It’s still being flagged by Norton as well.
duz 2017/04/27 at 03:35

Norton is no longer flagging it with the latest version (1.34.3.0).
Mihaela 2017/04/27 at 20:48

Virus detected by Avast when running the latest version, 1.34.3.0 – Win32:Malware-gen. It prevents the application from running, sending the infected file to quarantine. Please fix.
Jorge 2017/04/28 at 19:56

vkz.exe from v1.34.3 is still flagged by avast as of 28/4!!!
Stefan 2017/04/28 at 20:36

MS Defender doesn’t have issues with vk-z,

Probably PEStudio can help to debug that:
https://www.winitor.com/index.html
JeGX Post Author2017/04/29 at 17:17

I give up with all these false positive results. I replaced the 32-bit version of VK-Z by the 64-bit version in GPU Caps Viewer 1.34.3.1. Should be fixed now.
Jorge 2017/04/29 at 19:50

Thanks, no more virus alert!
Maybe you should contact avast about this issue.
Btw, if you replaced the 32 bit version with the 64 bit version, then that means no 32 bit support for vk-z or what?
mathiash 2017/05/08 at 06:19

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).
1. mathiash 2017/05/08 at 06:34
  
  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.
mathiash 2017/05/08 at 18:58

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.

Especially newer demos shouldn’t kill one’s graphics drivers (and even more drivers, never mind) when touching the window frame. Disagree?
1. JeGX Post Author2017/06/12 at 11:27
  
  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…
jerry 2017/06/08 at 07:16

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.
1. JeGX Post Author2017/06/12 at 11:27
  
  Thanks for the feedback Jerry, I will fix the bug in the next release.
SH C 2017/06/26 at 22:58

Is there a way to select OpenCL platform through command line? In one of the example batches you have “/cl_device_index=0” but I see no way to select OpenCL platform.

Thanks.
Lian 2017/07/01 at 17:50

Caps Viewer crashes with phong lighting and normal mapping of the Vulkan 3D Demos on my GTX1080. Running latest drivers. If you mail me, I’ll provide any necessary logs.
1. Lian 2017/07/01 at 20:10
  
  Addendum
  
  My sincerest apologies – Riva Tuner Statistics was running. Once disabled, all worked 100%
  1. JeGX Post Author2017/07/24 at 11:51
    
    Thanks for the feedback!
Jorge 2017/07/21 at 02:35

I found a bug in v1.34.4.
I recently updated to a GT 1030 (GP108) and now GPU caps viewer shows both fillrates (pixel & texel) as 0.0.
This is obviously wrong!

Please fix it!

thanks!
1. Jorge 2017/07/21 at 02:35
  
  Upgraded* (instead of updated)
2. JeGX Post Author2017/07/24 at 11:47
  
  Weird, the GT 1030 should be supported by GPU Caps Viewer. Could you post a screenshot of the GPU panel?
  1. Jorge 2017/07/24 at 18:35
    
    How do i attach a SS here????
    1. JeGX Post Author2017/07/25 at 19:33
      
      Try a free image hosting like TPU’s one:
      http://www.techpowerup.org/upload.php
Jorge 2017/07/26 at 03:26

thx, there you go:

http://img.techpowerup.org/170726/gpucaps.png
1. JeGX Post Author2017/07/26 at 11:09
  
  Ok I think GPU Caps 1.34.x.x does not support the GT 1030 (the GPU monitoring lib has not been properly updated). The new version 1.35 will fix it. I should release it today.
  1. Jorge 2017/07/26 at 21:20
    
    thanks, I’ll be waiting!
    1. JeGX Post Author2017/07/28 at 14:23
      
      GPU Caps Viewer 1.35 released:
      
      http://www.geeks3d.com/20170728/gpu-caps-viewer-1-35-x-released/
      
      Let me know if it works better for you.

Comments are closed.