GPU Caps Viewer 1.41.0 released

Started by JeGX, December 31, 2018, 02:58:50 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

JeGX

GPU Caps Viewer 1.41.0.0 has been released.

Release notes and download links:
https://www.geeks3d.com/20181231/gpu-caps-viewer-1-41-0-released/

Quote
Version 1.41.0.0 - 2018.12.29

+ added NVIDIA Titan RTX support.
! GPU panel and multi-GPU support: when it's possible, Vulkan,
  OpenCL, CUDA and OpenGL data is linked to the selected GPU.
  Useful when you have an Intel GPU + an NVIDIA or AMD GPU.
! updated CUDA panel with new information (bus id, mem clock,
  mem bandwidth, L2 cache).
* fixed a bug in GPU program initialization (OpenGL) in the
  kx framework of GeeXLab demos: the GPU programs were not
  created on Intel GPUs.
! updated with latest GeeXLab SDK libs.
! updated: GPU Shark 0.12.2.0
! updated: ZoomGPU 1.22.2 (GPU monitoring library).

GPU Caps Viewer + GeForce RTX 2070


mik


Stefan

#2
Quote from: mik on January 01, 2019, 02:14:03 AMThere is a wrong EUs number for my HD630, it should have 24 EUs.
Indeed the number of EUs should match the CUs in the OpenCL field.
24x8=192 - somewhere in the code bits and bytes are mixed up?
Also double-check with GPU-Z.

JeGX

I updated the GPU info in new GPU Caps Viewer 1.41.1.0 . So far, I displayed the number of cores and called them Execution Units which was wrong. Now, the number of cores and executions units are displayed at the same time.

JeGX

A maintenance release of GPU Caps Viewer is available.

Downloads:
https://www.geeks3d.com/20181231/gpu-caps-viewer-1-41-0-released/

Quote
Version 1.41.1.0 - 2019.01.04
+ added GPU power info (min/max values) for Radeon HD 7000 series
  in the GPU panel.
! Intel GPUs: now the number of cores and EUs are displayed in the GPU panel.
* fixed crash during startup on Radeon HD 7000 series
  like Radeon HD 7970 or Radeon HD 7850. The crash was caused by the reading
  of PowerTune info (OverDrive5 only) in the GeeXLab GPU monitoring plugin.
! updated with latest GeeXLab SDK libs.
! updated: GPU Shark 0.12.3.0
! updated: ZoomGPU 1.22.3 (GPU monitoring library).

JeGX

A new maintenance version has been released:

https://www.geeks3d.com/20181231/gpu-caps-viewer-1-41-0-released/

Quote
Version 1.41.2.0 - 2019.01.04
! Intel GPUs: only EUs are displayed in the GPU panel.
+ added detection of additional Intel UHD 630 and
Iris Plus Graphics 655 GPUs.
! updated: ZoomGPU 1.22.4 (GPU monitoring library).

JeGX

A new maintenance version of GPU Caps Viewer is ready.

Downloads:
- https://www.geeks3d.com/20181231/gpu-caps-viewer-1-41-0-released/

Quote
Version 1.41.3.0 - 2019.01.16
+ added support of NVIDIA GeForce RTX 2060.
- dropped support of Windows XP.
! updated with latest GeeXLab SDK libs.
! updated: GPU Shark 0.12.4.0
! updated: ZoomGPU 1.22.5 (GPU monitoring library).

Leo

Hi,

I meet a problem and need help.
When I run GPU Caps Viewer 1.41.3 with 3D Demos - OpenCL CPU - 4D Quaternion Julia Set, it popup "OpenCL CPU not supported on the selected platform". Does it mean my CPU is not support?

My system is a Laptop and that is Intel CPU + NV GPU, thanks.

JeGX

If your graphics drivers (Intel + NVIDIA) are correctly installed, you should have OpenCL CPU+GPU on Intel platform and OpenCL GPU on NVIDIA platform. Then you have to select the device you want at the bottom of the OpenCL panel and run the demo.

Also, look at this article, maybe it contains few hints that will help you.

ajay_bas

When running tests from scripts\Start_All_Benchmarks.bat, results do not seem to be showing on bench_result.csv
This was not an issue in previous versions (1.32.0.1)
Moreover, when some tests do post the results, they don't seem to be appending on the same file.

JeGX

Thanks, I will look at the issue for the next release.

ajay_bas

Any estimated time on the fix?

Quote from: JeGX on March 13, 2019, 12:07:27 PM
Thanks, I will look at the issue for the next release.

JeGX

I will try today or tomorrow if possible  :P

ajay_bas

Quote from: JeGX on March 21, 2019, 11:10:21 AM
I will try today or tomorrow if possible  :P

Hi,

This problem still exists on the latest - 1.42 version.