Quote:
Originally Posted by andreiutzu21
the dot is not there after the 0 but at VRAM is the same it shows 3 gb instead of 4
|
That VRAM without problem.
THE STORY:
The CIU formerly at the time of Yener90 used the get_hw_caps.dll library to detect hardware.
As some functions stopped working with this library after the release of new versions of windows, the CIU started to use the ISSysInfo.dll library (by petef1999).
However, after the emergence of GPUs with VRAM greater than 4 GB, this library began to not correctly detect the VRAM of these GPUs.
Then I searched for efficient hardware detectors for VRAM, until in "CIU 3.0.0.0_b9.u1.HF6" I made my own version in the CIU script itself getting the values in the windows registry, but using the same ISSysInfo library .dll to read GPU name
But that wasn't so efficient because as you commented the labels were smaller on "CIU 3.0.0.0_b9.u1.HF6" (see it has 2 video card names).
What happens is that in idle mode, current laptops turn off the dedicated video card using only the integrated Intel HD Graphics card.
So after that in "CIU 3.0.0.0_b9.u2" Razor12911 helped me by improving a code which he himself had shared in the debate about not having a functional VRAM detect code so that this code would not only detect Namee VRAM of all GPUs and generate a list. Now it ordered and returned only the highest VRAM value (a logic because the dedicated card would probably always have the highest VRAM).
So I inserted Razor12911's code into CIULib.dll trying to make the VRAM check faster than the script itself using my code.
Now I perfected my script code to not only get the largest VRAM, but also read the name of the current GPU that has the largest VRAM size (I hope it's not slow).
I will send you a PM soon with test file.
If possible send me by PM the original captured images of your previous post b9.u1.HF6 (the labels are illegible).
Thanks.