This new version of GPU Caps Viewer adds the support of Intel Ivy Bridge GPUs (HD Graphics 4000) as well as the support of some AMD’s Mobility Radeon GPUs. For OpenGL programmers GPU Caps Viewer 1.15.0 re-activates the GLSL shader validation utility (Tools panel). This simple tool allows to check the compilation of a particular type of GLSL shader. All types of GLSL shaders are now supported: vertex, pixel (or fragment), geometry, tessellation control and evaluation.
Download
You can download GPU Caps Viewer 1.15.0 here:
Webmasters: hotlinking is not allowed (that will cause an error message), please use the post url as download link.
|
|
Win32 installer: [download#274#image] Zip archive (no installation required): [download#275#image] |
What is GPU Caps Viewer?
GPU Caps Viewer is a graphics card information utility focused on the OpenGL, OpenCL and CUDA API level support of the main (primary) graphics card. Even if you have several graphics cards in your system, only one is considered as the main OpenGL or Direct3D device. For 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 Caps Viewer 1.15.0 changelog
- New: (re)added GLSL shader validation utility (vertex, pixel, geometry, tess control and tess eval) in the Tools panel.
- New: added detection of Intel Ivy Bridge HD Graphics 4000 GPUs.
- New: added detection of some AMD mobility GPUs (WinterPark, BeaverCreek).
- Update: ZoomGPU 1.6.3
there seems to be a small naming error for the glsl validation buttons…there are 2 buttons which are named “pixel shader”. one of them opens the geometry shader dialog…
The install directory is GPU_Caps_Viewer_v1.14.6 instead GPU_Caps_Viewer_v1.15.0
Thanks guys for the feedbacks. I’ll fix these errors asap!
Hello. After reinstaling of Win764bit have instaled AMD driver for my Sabertooth 990FX MB, using 560Ti for OpenCL app and cannot set it in that app. drivers are instaled, GPU CAPs see that a OpenCL Nvidia is here but even the AMD CPU driver for OpenCL is present. How can set that my app see the Nvida OpenCl device ??????
Hi JeGX, I’m trying to use AMD CPU and NVIDIA GPU on a same OpenCL application using OpenGL interoperability (I’ve a system with 1 AMD CPU (Phenom II X4 965), 1 AMD GPU (Radeon HD5870, hooked to the main display) and 1 NVIDIA GPU (GeForce GTX460, hooked to the secondary display)). When trying to create OpenCL context for the HD5870 from the OpenGL contexted created previously (using GLUT), all goes fine, but when doing the same for the GTX460, I’ve got a NULL CL context and -1000 as error code (maybe because the GL context is created on the HD5870 card and not available for the GTX460). But you, you did it succesfully somehow, because GpuCapsViewer is able to run CL GPU codes (all example codes) on the GTX460! How you do it?! Do you use some sort of glSharelists in order to share GL context from the radeon to the NVIDIA? Is it possible for you to share some insights or code lines on this matter?
Cool program. Can we get a Linux version now?
The benchmarks run on wine, but it can’t get all of the info about the GPU.
In OpenCL tab information about CL_DEVICE_OPENCL_C_VERSION must be added. See here why: http://forums.nvidia.com/index.php?showtopic=207170&st=0&p=1295650&#entry1295650
Does not show the Internal Intel GPU 3000 as second GPU on devices list although Windows 7 does. Also need some Directx11 information.
Nice utility. Thanks for making it available