Leeghoofd

K I just talked with the graphics designer, 1st of May there will be a background lads

WHy U nO pOsT 4 min 14sec?

not allowed in this competition....

You must win this stage to avoid that ?

I deleted them all, plz resub the one you want to be upped

For 2D, CPUZ for CPU & Memory. For 3D, CPUZ for CPU and Memory plus GPUZ. For competitions additional validation can be requested

CPUZ tabs for CPU and memory are in the rules, motherboard, SPD tabs are optional

The golden boy is back

Done

Look at this guy leading the rankings, go go Peter

Tight battle

recalced

If there's one game that is the perfect example of too many rules that must be football... Many referees interpret them in their own way, mostly being pressured by the heat of the moment or the lack of time to take a swift decision. Even the VAR ( especially in Belgium) is drama and allows maybe only 80-85 minutes of effective playtime and even its decisions are hit and mis. Again confused by correct implementation of the abundance of rules Remember there is no benchmark that can't be broken/bugged, not even BM is fully bulletproof in clock detection, but its the best and most secure we can get, thx to Mat's hard work. However that would limit us to the integrated BM suite... Which in the end would become boring as we are looping the same set of benchmarks over and over again... We have to wait if Mat can integrate a new benchmark into the BM suite. But everyone wants to avoid another Geek drama, so it better be handled officially. Again the initial rules were set at 5206Mhz , though XTU detected for some users 5.22. So we changed the rules for the better and allowed 5.22 XTU and to give users to opportunity to bench at real 5206Mhz clocks. Now if you can bench and XTU detects 5.22 but CPUZ detects 5246Mhz, (even if only for one second) than you are in the grey zone as your score did the exact opposite of what everybody was experiencing before. Changing rules is non standard, but two 2 days before the end of competition a poll is impossible to do.. FYI we have discussed the G.Skill Tweakers on Discord amongst participants, so its not a "now let us do this my way thingy". I have to rely on common sense and use my peasant logic... Which is really the only way to survive in this place as a moderator ?

This particular mindset is what lead to all these rules/limitations at the Bot... Remember what was the inital rule ? I guess it was 5206Mhz. People benched it and it turned out that XTU reads out 5.22. Now you guys bench 5.22 XTU but CPUZ reads out 5245Mhz... Try to explain it to me... Logic prevails, ever thought why do you think we ask CPUZ too and not only XTU benchmark window? Who's really bending the rules like rubber? Oh it's not stated in the rules, so we can abuse it and clock up higher coz XTU doesn't detect it properly... Nice try lads, insert coin and try again... Try to beat the systems, guess what the system always wins... Now if you insist I can still add hwinfo too...

score removed...

We had some talks with the programmer as memory models could get subbed in the wrong category, messing up the validity of the Database: e.g. G.Skill Ripjaws (DDR3) end up in the DDR5 category. So he will add in the future some features in the Database to prevent this from happening. Also to keep his workload more ecnomical he proposed to move from the old memory tree layout to a corresponding model like with the motherboards.

I'll delete this one , just resubmit it , but don't forget the CPUZ tabs for CPU and memory as stated in the rules ( https://hwbot.org/rules?referenceId=5289 )

I'll delete this one , just resubmit it

I'm cleaning up the memory submissions, so hopefully next week no more GTX 2 in DDR2 category and other mixups (due to bad DB design) We also removed some no longer used/unsupported benchmarks and their submissions yesterday to trim the Database. We had many duplicate benchmarks, some with zero subs (user made) and some couldn't even be submitted to anymore due to lacking developer support.

So only RV710 core, no other restrictions gents ?

no problem, it's a goner!

Everything is put into a queue sir, so sometimes it could take a while if e.g. a huge recalculation is ongoing. How long? that can vary from a few sconds to half an hour. Hopefully we can speed up things in the summer with the new hosting

Can I tell you the bot gets confused if you sub 4 times the same score? Why does one think it will be better if one subs it 4 times?

As expected but dissapointing nevertheless...(talking bout the CPU PJ :p) Guess this will remain a nice reviewers CPU to test tech for the future...

We found the hidden ones Gregor and moved them to the (-F) variant, deleted the old non F