TeamAU

i'm not going to engage in whatever fight youre* looking for because the poll has gone against your wishes Roman do the right thing

absolutely pathetic is you attempting to punch back in such a way. im trying to talk to you with respect and you feel the need to push things in another direction. im not sure if you feel you get to talk to people such a way way because of your social media status? its certainly not from overclocking as your not in the right tier to come at me in such a way. take a step back and make the right decision Roman

seriously? splave benches for asrock? who would have known? thanks for the update kid

Roman you're a reasonable guy that makes informed decisions, that's why your NOT going to make CPUZ benchmark all cores/threads 1. the community has voted, you can go against this, but all that stuff you said about HWBOT saying community based goes out the window, you lose the right to say that anymore. regardless if its true or not, this looks like asusbot, thats not good for you, the community or asus 2. this looks really salty on the back of the gigabyte beating asus, regardless if its true or not, that's how everyone is interpreting it and thats fact 3. lets look at this logically, are we going to start making people run superpi with 8c/16t? pifast? memory validation with whatever the default timings are? this is what we do, whatever is required to reach the highest frequency possible. if its amd is with all cores at 1.6ghz except the valid core, if its memory at 1000-1000-1000 whatever is the highest possible timings are, bring it on, we want to see the highest frequencies/scores ever. this is extreme overclocking! lets leave whatever has just happened between companies out of this and make a logical decision

in my personal opinion there's no real challenging between until the comp finishes as we really dont know what scores are real and which are place holders anyway we have a way we do things with internal competition for each benchmark and pushing each other to achieve our best day in day out over the course of the competition we don't use other teams scores as a target, we don't trust operating systems or drivers other teams are using, we test everything we can, push the platform as hard as we possibly can and don't give up until there's nothing else to try or test.... if you've done this and you can't do any more, you can be proud of your result weather you come first or last, plus spending time with friends and sharing/learning from other overclockers in your country, this is what CC is really about

thanks for organizing Alby it was a great comp, the crazy amount of stages were draining, difficult, required a real team effort, but also rewarding and fun i thought i would hate the ycruncher one but loved it, loved the REX 32m stage, enjoyed 06, a lot of our guys loved the AMD stages lets go for 28 stages next year with 15 subs in each!

hey alby in the early stages you said gpupi 3.3 for the AMD CPU stage, is that still a thing? Or are we capped at 3.2 for both? the GPUPI for GPU stage says 3.2 limit, the CPU stage doesnt mention Cheers

just woke up and looked at everyone ??

Unfortunately zerodan and micka are using the wrong nvidia driver version so both will have to be disqualified Both unfortunate as they put up great timespy scores

Thanks for working this out alby and rich

hey Alby, Pete is just trying to submit his gpupi 2.3.4, its not accepting his submission, erroring with invalid version when submitted this thread says 'Stage 3: GPUPI-1B version 3.2 or below' and the GPUPI rules page itself says 'V2.3 (mandatory from August 1, 2016)' http://www.hwbot.org/news/11973_application_145_rules/ can we please make sure this submission is accepted as all official stated rules were adhered too thanks

yeah great score, lets hope that 2080TI comes into play soon

you guys have been doing a great job over the last years, except for 3d11 on vega, that sucked!

Matt's had a legitimate question that he just had a bit of a joke with, it wasn't offensive, it was light hearted Thanks Alby for the info also

im reporting this for sale thread for not having the latest systeminfo

im putting out the challenge to all the big guys next year get involved in Country Cup, this is my most enjoyable benching of each year, an excuse to catch up with good friends, bench old stuff that i normally wouldnt touch its genuinely alot of fun, but if the top guys from each country dont turn up and show the up and coming guys how its done, we are going to keep coming and taking this every year dont let us win 2018

okay heres a possible solution great so new version fixes memory hack, but lets increment the version again, make it the new only allowed version on hwbot fix the score calculation, remove the dependency on CPU frequency from the scoring, right now if you trick the system into thinking its 7ghz, you get a higher score, so the benchmark is using the CPU frequency in its scoring algorithm, this needs to be fixed changing the scoring algorithm will possibly make some scores higher or lower than before, so purposely make the new version score higher, over time everything will be rebenched and any existing cheat scores dont even matter NOW is the time to fix this when we already have a problem to fix

this is really irresponsible whoever published this video showing everyone how to hack XTU many years ago CPUZ was vulnerable to this type of ram editing attack, however through working with Franck privately we could stop this happening in future CPUZ version, without publically announcing to everyone how to do it the problem we have is, a handful of other benchmarks will also be vulnerable to ram based attacks and now its open slather for whoever wants to do it i understand that XTU is a big money card around here for HWBOT and they need money to keep going, but is this the end of the road for XTU? we already know XTU uses a fake algorithm that takes into account the CPU frequency into calculating the score and can easily be tricked into giving incorrect scores, if XTU wasn't so linked to sponsorship this would have been removed years ago. Can we consider letting it go?

why do you want him banned so badly?

This wll ties together though, we cant go and witch hunt someone when others had no punishment for a worse crime

Pcmark there was never any files replaced in the benchmark itself, cine the rendered graphics file was replaced with something easier to render Its like shortening the race track and then comparing your result to ppl that raced the full track

Cinebench is way worse than this, this is manipulating the os to skew the benchmark Cine is directly editing the benchmark for a different result, there is nothing worse than that

I can relate to s@ position, when i first arrived i took many big records and was doing it with less clocks than most of the big guys at the time, i had alot of negative feedback and had to prove myself over and over again Im not defending his actions, but because he pushed the boundary in a few benchmarks doesnt mean his amazing 3d scores are invalid All you guys jumping on the ban wagon that were cheating at cine should take a good long look in the mirror

I also dont know the circumstances with the cinebench situation other than how the cheat worked, however i tend to agree with some of the guys there questioning thr handling of that situation verses this Afaik, please correct me if im wrong, no bans were given during the cine situation, yet the manipulation of the benchmark was imho worse with files being replaced in that situation than x265 where its a timer issue, dont get me wrong, both are bad, but any time your editing files in yhe benchmark itself its as bad a cheat as you can get Im not calling for bans or no bans, honestly i dont care thr outcome, but i do call for consistency Even if it's not the case, we cant be seen to be giving leniency to more well known users in a more serious chesting case, and then immediately banning a lesser known user at the first chance we get Lets treat all hwbot users equally

sick benching man, this is proper OC right here