Jump to content
HWBOT Community Forums

richba5tard

Administrators
  • Posts

    6082
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by richba5tard

  1. Not me, but I think the top 6 of the g.skill qualifier have been confirmed. http://oc-esports.io/#!/round/gskill_ocworldcup_2018_qualifier
  2. I think I agree with Massman. Being a douche at the forums does not make you submit invalid scores on hwbot. Being banned from making submissions does not mean by definition we should mute your voice on the forums.
  3. The "Only use processors from the sub family. - your submission is incomplete" should be resolved now, can you retry?
  4. competition points are fixed now too. be aware only the division you selected in your account count!
  5. Got to act fast if we need to configure a new benchmark in hwbot and the competitions.
  6. Right, road to pro points. Darn, sorry about that. Just one more thing to fix (tm).
  7. Manual approval of WR's has been talked about since the beginning of HWBOT, but requires manual resources we don't have, and is a PITA during competitions where new hardware is launched. Sandbagging & WRs would not go together. In the meanwhile I was able to reproduce the submit WR & delete issue, which is now fixed on production too. As a side effect it takes a long time to delete a WR, but I can make this asynchronous in the future. This was the last reported issue of rev7.1, if I ignore the old (pre rev7) issue that some submissions are incorrectly marked as "best submission of a user" and appear twice in a ranking.
  8. I've configured it as per documentation given to me by leeghhoofd. It explicitly said v3.3, so I asume it's not a mistake. @Leeghoofd
  9. Thanks George! - edit: Okay, triggering a recalc of position #1 fixes this, but now I've got to find out how it was possible that the points decreased all of the sudden. I think the most likely scenario is someone submitted a wrong pifast world record (eg 8 seconds), which triggered a full recalc with a new WR to compare to (making everyone lose points). After that, the submission got deleted, and the rankings did not recalculate (which they should). That is my current hypothesis which I'm trying to reproduce. Just thinking out loud so you guys now what is going on.
  10. If anyone spots a broken ranking, please make a screenshot. As the last reports always looked fine when I got around to check it. Thanks!
  11. Hi guys, I can configure competitions but I'm not up to speed in what's hot or not. If we do it the same as last year, I should configure the comp to start tomorrow. Shall I just configure the same benchmarks, but using this years hardware (intel 8th gen, ryzen, etc)?
  12. Thanks for reporting, looking into it tomorrow morning.
  13. I see 46.7pts for first spot going down to 14.6pts for 20th. Seems normal?
  14. 13 hours and no one complained. This is a new high for rev7!
  15. There was a temporary transaction deadlock when you submitted. it;s ok now.
  16. It's a bug alright but nothing to do with rev7.1 point calculation. The detection and marking of best hw/gl submissions is a seperate thing.
  17. 60% done @Alan_Alberino this has been discussed before.
  18. Correct due to score difference. Currently at 40% recalculated.
  19. Can anyone spot broken GPU 1B rankings? Or UNIGINE SUPERPOSITION - 8K? Those are already completed.
  20. Indeed, I can make it more robust but rev7.1 polishing comes first, otherwise it keeps distracting me. Recalc is 20% done after approx 20h, so I guess it will take 3 - 4 days to complete.
×
×
  • Create New...