websmile

Seems the case will be not cleared here - maybe take a lawyer. I banned the seller from marketplace and indefinitely from hwbot, his access at forum is still valid for some weeks if he decides to contact you here and solve the issue in a civilized manner. Then I will ban him from this as well because hwbot is not tolerating this behaviour and obvious scam at all.

The stage rules are too long mostly, and some people do not bother to read them, I just had this at division 1 as excellent example. Nontheless I think this is OK, I did this for all divisions but it got lost for pro oc obviously. On the server issue we will never be on same opinion, for me it is like using a truck or a traktor at a formula 1 or nascar race

Just saw this - yes, you obviously did not read my post despite quoting it and you did not read or understand the rules - when I write pro oc I mean pro oc, and when the rules say no hedt, say 2066 is forbidden and explicitly list all allowed cpu families and KBL-X is not listed it must be really hard to not understand^^

No server hardware at all, we always clearly says desktop hardware only unless stated otherwise. This topic gets that annoying that I really consider a proposal banning all server hardware from hwbot. No one needs this cr.. apart from business guys...

Dividing by core makes no sense on time based benchmarks, more cores are faster, if you divide by core you only enhance the advantage of eight core against quad core for example. The rumble is balanced so that sometimes more cores are better and sometimes dual core can win due to core division

Vega is not allowed but this should of course be clear when it was released long time after the competition started. We cannot technically block submissions with hardware that does not exist at start, but I will now create a task that subs will not be accepted any longer and I will remove the vega results in all divisions sooner or later

Sent you a pm

For LN2 Formula or Extreme ROG are best Asus boards, Gene is good as well but allowes lower memory voltage. OCF refers to Z77 OC Formula by Asrock, yes.

There is a high chance that the board or cpu might limit you then. If you enabled pll overvoltage and set right imc voltages normally 2600c9 should work on Elpida bbse or similar ics which your kit most likely uses. Maybe you can check on a friends board first, but an asus rog z77 board is usually a quite good choice, or an OCF

This might be the ic characteristics, BBSE and similar Elpida chips are often opting out at 2400 c7 - try 2600 9-11-9 or 9-12-9 to check if the board limits you.

You can ask at Galax, for the standard retail HoF I cannot provide working tools. The GOC pack is exclusively locked to work with special Lab GOC edition only

You have to submit XTU for competitions at oc esports website for the stage - the problem is caused by XTU normally not in need of a screenshot for validation, which means when you submit at hwbot.org you add the screenshot as rig picture in fact. This is not accepted when you try to add the sub to the comp then. As said, the solution is subbing at oc esports website via submit button of the stage

Memtweakit shows Apex

As said, Havli is checking options and sacrificing his time to fix the flaw, and we are thankful for this. I am very optimistic this will come soon, maybe 2,1, he will decide this

We can see the cheat but the developper works on the program to make it more safe so mods have less work at checking, For challenger nothing is changed

Disallowed tweaks/cheats Any software or human interaction altering the perceived speed of the benchmark program, tricking it to believe it ran faster I think for x265 and the rules, I quote them again, you can´t talk of not cheating. It is a deliberate act to pause the benchmark, it is visible the result is not obtained correctly because of the time elapsed and one or two other issues. I was very fond of $@39@ from the start of his comeback and always willing to help, recaculate scores, answer questions and so on and it is no fun for me to see this situation now. It also damages hwbot once again. On Hwbotprime, it might be eol, but I had never the problem you mentioned with paused benchmark for example. If I would get a dollar for each 3dmark, catzilla or 2d benchmark I had to block for being bugged runs or which I saw (including spi 1m pifast etc) I could buy cpus at palettes . As long as we have thousands of different variations of os, drivers, stripped copies etc we will always face bugs even at the most reliable benchmarks. But bugs and cheats are a different pair of shoes...

Hwbot prime has been used for 7 years or more - if you think this benchmark is insecure (which now was proven by a lot of criminal energy) you should test a lot of other benchmarks hwbot considered for ranking once. It is a simple fact that there is no 100% safety, what you ask for is something no bank nor any billion dollar company can offer, otherwise there would be no hacks on online banking or exploits. We have benchmarks developped by companies that are much easier to manipulate than hwbotprime for example

You did read what I wrote? For Pro oc 7740K is allowed, there is no word about division 1. HEDT was never allowed nor even thought about for other divisions, the 7640K is not allowed for division 2 for example as well.

This situation is by no way comparable with the cinebench desaster. Hwbot partially was responsible for this by making cr.... rules. It was not mandatory to show the rendered image, neither in parts or in full and apart from a paragraph at general rules there was no hint on file editing (people should have known better, but loophole searcher are what we see all the time). We have no time measurement and no validation file at cinebench, and in fact banning people would have been a good idea, but the simple question of whom to ban, whom not and the high possibility of error lead to noone being banned because proof was really hard to get. I think hwbot learned from this, and it is no matter of Elite, extreme or enthusiast league. We applied a lot of bans last nine months, more than we wanted, and it did hit high ranked guys/ known ocers from all leagues now. Wish we could handle this differently, but like in all sports and competition cheat happens, and all we can do is to apply the rules. Minor violation, minor sentence, big cheat, long ban.

For pro oc the 7740k is allowed because challengers started 1.08. Different story than on team cup which started 1.07.

Only acceptable for mobile because of the restricted resolution options on most of them.

Yep, I forgot that he did not use overkill mode.

In fact this was not aiming at your score with 970 because I saw the video already, this run is most likely bugged or driver related but for sure not manipulated with a time shift. The 980 run for example is perfectly in line.

Well, the time is 2s slower than on second place but result is higher, on splaves results it is the opposite, faster time= higher score like in the rankings. On heaven the results I checked have extremely low minimum fps but extreme high maximum fps compared to other results, this made me wonder if a in benchmark time boost accelerating fps like a fast forward might be problem, but it can have lots of reasons

Is this "tweak" tested to work on 1151 as well or is this just speculation now? And second point, does it work on benchmarks with point based result only or also on time based results? And third point, I have a list with some weird 3D results, is it possible stuff like Unigine Heaven for example or FM benchmarks are affected as well? Thanks in advance