Quote from: hawks5999 on June 22, 2011, 11:17:07 PM

So I've tweaked this a bit. I saw where one of my rigs kept falling back to default core so i set up an -a all -c to refresh the OC as a scheduled task. but now i've put it into the monitor batch and set to run every 5 minutes with the monitor refreshing every 15 seconds

[...]

i'd like to add the -c value as a variable and have that variable set to different speeds based on temperature. so if it hits a threshold, say 80C it would clock down by 30mhz or so. and then when it gets back to a reasonable range, crank it back up. i just hate doing all the for %%i TOKENS crap you gotta do to parse output. I'm sure for someone who's done more batching it would be trivial to write though.

I hope your card is not throttling down because of overtemperature. Also you might want to try to get rid of the autostarting ccc process (e.g. with spybot) maybe that is resetting the clock for some weird reason.

if you run clocktweak in a loop make sure there are no other programs running that access the gfx drivers! Especially with 10.x drivers things will probably get unstable.

It was really cool to have:
1.) a sweetspot finder
2.) artefact and temperature limited overclocking control = permanent optimization

I thought about these functions quite a bit but it would take a lot of time to implement.