I was trying to OC with my card, and I came up on this post that if you OC shader and core clock separately you will have better performance, IE leave Core clock at a stable OC while keep pushing shader (if it is stable). Now everything works fine, until I change shader to 1215 and Clock is set at 560, Mem at 400 which should be reasonable since I can do 600 Core and Mem stable when they are linked. I test it with ATITool running the hairy cube, the FPS is now half I use to get 200+ fps as average now it runs at average of 90 barely, I thought I was screwed so I defaulted the clocks and restarted the system, but it still does the same thing, I then ran 3dmark06 at default clock and got 3100+, and ran a few games; it seems like the performance in other application isn't affected, but only ATItool which is reading the right clocks and everything just crap performance in it's 3D mode. Reinstalling the app doesn't seem to help...
It is not a too much of an issue since 3D application seems to still run at max perf but with ATItool cripple, it really annoys me. Anyone else had this problem?
-
I thought if they weren't linked it screwed your timing.
Weird ATITool FPS counter Problem.
Discussion in 'Gaming (Software and Graphics Cards)' started by Dragonpet, Jan 24, 2008.