TeamAU

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

see you guys soon, lets drink some beer together!

is this your "last hurrah" before retirement?

2016 is yours bro, congrats

lol did you just bench asrock? hes not a 1 vendor man anymore!

scores maney bro

nice result

great result guys

wow thats a nice one

EZ for ence

im not attacking, im just legitimately saying im concerned with the way it calculates points