Well that didn't take long from 0.1.2
1) It's telling me it has 8 ROPs, when the two links below show only 4
2) (I'm assuming because of the ROP issue) the pixel fillrate and texture fillrate are double what they should be.
http://www.gpureview.com/GeForce-6600-GT-PCI-E-card-187.html
http://en.wikipedia.org/wiki/Comparison_of_NVIDIA_Graphics_Processing_Units#GeForce_6_series
It still seems to not kill the actual process if i look in task manager. This is causing the "open two, can't open any more!" issue people seem to be having.
EDIT: On a good note, it doesn't kill the backlight on my laptop anymore!
EDIT: GPU-Z now decides it wants to use 85-99 of my CPU performance, constantly. Comparing my dual core laptop to my single core desktop, it seems each instance of GPU-Z thinks it's entitled to use up one full core. 50% CPU utilization on my laptop, 100% on my desktop.
EDIT: The above CPU utilization bug ONLY seems to happen if I let it check for a newer version. If I hit close before it finishes checking I don't get this bug, or the one where the process itself stays running after I close the GPU-Z window.
1) It's telling me it has 8 ROPs, when the two links below show only 4
2) (I'm assuming because of the ROP issue) the pixel fillrate and texture fillrate are double what they should be.
http://www.gpureview.com/GeForce-6600-GT-PCI-E-card-187.html
http://en.wikipedia.org/wiki/Comparison_of_NVIDIA_Graphics_Processing_Units#GeForce_6_series
It still seems to not kill the actual process if i look in task manager. This is causing the "open two, can't open any more!" issue people seem to be having.
EDIT: On a good note, it doesn't kill the backlight on my laptop anymore!
EDIT: GPU-Z now decides it wants to use 85-99 of my CPU performance, constantly. Comparing my dual core laptop to my single core desktop, it seems each instance of GPU-Z thinks it's entitled to use up one full core. 50% CPU utilization on my laptop, 100% on my desktop.
EDIT: The above CPU utilization bug ONLY seems to happen if I let it check for a newer version. If I hit close before it finishes checking I don't get this bug, or the one where the process itself stays running after I close the GPU-Z window.
Attachments
Last edited: