October 27, 20168 yr If frequency and hardware detection work well we can neglect screenshots. Offline verification is a must tho. Even at Caseking I can't just hook up a random rig to the internet.
October 27, 20168 yr I wonder if Trouffman stated that beer is good, and European overclockers would turn it into a personal attack.
October 28, 20168 yr The futuremark sysinfo is not sufficient for proper verification. Frequency read-out is usually not correct. Sorry what? I can't hear you over my "0MHz" CPU
October 28, 20168 yr I don't have any problem with integration but I just can't stand sysinfo as it offen reads bull
October 28, 20168 yr Crew If frequency and hardware detection work well we can neglect screenshots. Offline verification is a must tho. Even at Caseking I can't just hook up a random rig to the internet. That is a BIG IF mate :celebration:
October 28, 20168 yr Id prefer this if given choice between no screen shot and this method or having to use a bench that is retrofitted with a wrapper. The history of wrappers being added to benches......
October 28, 20168 yr Members Id prefer this if given choice between no screen shot and this method or having to use a bench that is retrofitted with a wrapper. The history of wrappers being added to benches...... Just wondering why? (get the feeling the wrapper and any drama about it was added whilst I wasn't benching)
October 29, 20168 yr Well.... if the benchmark would be killed consistently, then it would be ok to add to new additions to the selection As long as runs are standardised, the handicap is irrelevant Obviously it's only a problem when it's added to something that's had time without it.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.