trodas Posted October 5, 2013 Share Posted October 5, 2013 Guys, when overclocking or pushing for lowest possible clocks, there are usually plenty of runs, witch differ only by the clocks used. This is IMHO quite normal and one could save most of the time by just choosing the prepopulated hardware values from previous submissions... Or so I thought. But I was wrong! No-one can do that, because the GPU clocks are LOCKED and cannot be altered from the previous submission prepopulatd fields...! And I done some quite similar submissions: ...witch should not require re-entering all the HW over and over again (XTU not work on W2k...)... This is IMHO quite serious limitation and should be fixed ... please. Quote Link to comment Share on other sites More sharing options...
Christian Ney Posted October 5, 2013 Share Posted October 5, 2013 Yes that's a known bug. Unfortunately our programming force is not available at the moment so I dont know when it will be fixed but hopefully soon because it is very annoying. The way around is to use prep fields then edit your submission and put the clocks (fields are unlocked). Quote Link to comment Share on other sites More sharing options...
trodas Posted October 5, 2013 Author Share Posted October 5, 2013 Yep, I trying this - just edit the old and copy to the new... But that is very likely to create some errors, so it is not a best way... This and the DDR3-insist bug is quite annoing. Let's hope someone look at this soon... What can I to do help? ATM I only waste resources by finding too many bugs... lol Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.